A parks-department dashboard calls a Cisco API with a Bearer token, receives HTTP 401, then retries after a token refresh that the authorization server also rejects. What is the correct control-flow choice?
Select an answer to reveal the explanation.
Short Explanation
If both the door badge and the badge printer say no, standing at the turnstile and swiping forever does not help. Once the token hop has already failed, the consumer stops—it does not spin endless 401s.
Full Explanation
A missing or rejected Bearer token on a resource call is not cured by replaying the same header. After a structured re-auth attempt fails—or when no usable grant remains—the unrecoverable-error path is to abort. Infinite 401 loops waste quota, hide the real failure from operators, and never become a successful write or read.