This error in GSC is terribly vague and it is really hard to know what they are referring to when you see this in the reports. So, don't feel alone in finding this report confusing! When you see this report, you have to step through and see if you can find what error Google is flagging. Keep in mind, it can be a false positive too where Googlebot caught something odd during their crawl.
Along with WhereGoes and checking the Location as Stephen noted, here are a few other thoughts that might help you with debugging:
When you inspect the URL, what do you see when you view the crawled page? Does the HTML code shown match the redirect destination's HTML? If so, that confirms Google is able to follow the redirect successfully. You can also try testing the live URL to see if that returns something different (with the live test you can see the code and a screenshot which can make confirming this easier).
As another way to see what Google is seeing, you can test with Web Sniffer. Unlike WhereGoes, you can change your user agent to Googlebot and then test the redirect. (You can change your user agent in other tools too, including Chrome but I think Web Sniffer is easiest to work with.) That way you can confirm that the redirect works for Googlebot. It should but sometimes there is an odd configuration that prevents certain user agents from processing the redirect.
This error also sometimes seems to happen because the redirect times out. A good tool to measure this is Byte Check. Byte Check shows you the time it takes to process all redirects within the page load. So long as the redirect happens quickly, you should be okay. However, if the redirect takes, say, more than 150ms then that is a pretty slow redirect. Note that Google has never said that redirect speed is a problem but this is based on my anecdotal evidence working through these problems with various clients.
Finally, you blurred out the URL, but what was the URL's protocol? I've seen instances where you end up with redirect errors due to a "chain" that happens when a link redirects first to HTTPS and then redirects again to the final destination. It isn't a chain in the problematic sense but Google can sometimes report it that way. If that is the case, that is likely a false positive that you can ignore. You could also try to collapse that redirect chain to see if that resolves the problem.
If you can't find anything in debugging, then it is likely a false positive. In that case, it should clear out on its own eventually. You could try to get Google to recrawl the redirected page (for example, link to the redirected URL on a page you know Google crawls often, like the home page) as that might prompt Google to reconsider it more quickly too.
Location:to which the 301 redirect points? What do you get when you then test that URL?
Locationfield? I don't see it under the pages I referenced in my screenshots...
curl --head https://example.com/foo.html.