After fixing an IAM policy for a civic Oracle Function, an immediate re-invoke still returns NotAuthorizedOrNotFound. The matching rule and policy text are now correct. What is the most likely explanation?
Select an answer to reveal the explanation.
Short Explanation
The Function keeps a short-lived memory of its old badge—about fifteen minutes—so a correct new policy can still fail until that cached token ages out.
Full Explanation
Oracle Functions document that the resource-principal token is cached for about 15 minutes. Tightened or loosened policies therefore are not instantaneous. Developers who correct a policy and immediately re-invoke may still see the previous authorization decision until the cached token refreshes.