Skip to content

fix(core): cap provider retry-after delays at fifteen minutes - #45787

Merged
rekram1-node merged 1 commit into
v2from
retry-delay-cap
Aug 28, 2026
Merged

rekram1-node merged 1 commit into
v2from
retry-delay-cap

Conversation

@rekram1-node

Copy link
Copy Markdown
Collaborator

Summary

  • Session retries take the larger of the scheduled backoff and a provider-requested retry-after delay. That minimum was unbounded, so a buggy or hostile retry-after header (for example one hour) silently stalled the session for that entire duration.
  • Cap the provider-requested minimum at fifteen minutes before it raises the scheduled delay. Ordinary backoff behavior is unchanged, and requested delays at or below the cap are still honored exactly.

Verification

  • New runner test: a 60-minute retryAfterMs waits exactly fifteen minutes before the next attempt.
  • bun run test test/session-runner.test.ts: 174 pass, 0 fail.
  • bun typecheck passes in packages/core; formatting and diff checks pass.

@rekram1-node
rekram1-node merged commit 7b6b0f2 into v2 Aug 28, 2026
10 checks passed
@rekram1-node
rekram1-node deleted the retry-delay-cap branch August 28, 2026 00:23
jinhuang712 pushed a commit to jinhuang712/opencode that referenced this pull request Sep 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant