Walk a stuck agent run with OODA
Recover a stuck agent run by separating observation, orientation, decision, and action.
Stuck run The customer-briefing agent is looping on the same CRM lookup. The meeting starts in 42 minutes, and the last trace shows one successful notes retrieval plus repeated 403 errors on revenue fields. A stuck run is not automatically a bad prompt. It may be permission, missing data, rate limit, tool schema, or an impossible task. OODA recovery Observe -> Orient -> Decide -> Act Use the loop to avoid random retries. Each step narrows uncertainty before the next action. Retry Fast, but it can hide the failure mode. The run recovers without destroying evidence or widening tool access…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in