Skip to content

Improve error handling and test reliability#27092

Closed
agents-git-bot[bot] wants to merge 1 commit intoproductionfrom
sync-docs-pr-301
Closed

Improve error handling and test reliability#27092
agents-git-bot[bot] wants to merge 1 commit intoproductionfrom
sync-docs-pr-301

Conversation

@agents-git-bot
Copy link
Contributor

Summary

Syncs documentation for sandbox-sdk PR #301: Improve error handling and test reliability

Changes

New Documentation

Added /sandbox/concepts/error-handling/ page documenting:

  • HTTP status code semantics: 503 (transient) vs 500 (permanent) vs 400 (client error)
  • Automatic retry logic: 2-minute budget with exponential backoff (3s → 6s → 12s → 24s → 30s)
  • Capacity limit errors: Production-only errors with specific error codes
  • Account limits: Current limits for Workers Paid plan
  • Best practices: Resource cleanup, automatic timeout, monitoring

Key Points

  • SDK now uses proper HTTP status codes for better error handling
  • Only 503 errors trigger automatic retry (transient conditions)
  • 500/400 errors fail immediately (permanent/client errors)
  • Includes practical examples and code snippets

Related Resources


🤖 Auto-generated by docs sync workflow

@github-actions
Copy link
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/sandbox/ @whoiskatrin, @ghostwriternr, @cloudflare/pcx-technical-writing, @cloudflare/ai-agents

@github-actions
Copy link
Contributor

github-actions bot commented Dec 12, 2025

Documents HTTP status code semantics, automatic retry behavior, and
capacity limit errors. Helps developers understand when errors are
transient vs permanent and how the SDK handles retries.

Synced from cloudflare/sandbox-sdk#301

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@github-actions
Copy link
Contributor

Hey there, we've marked this pull request as stale because there's no recent activity on it. This label is helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant).

@github-actions github-actions bot added the stale label Jan 19, 2026
@kodster28 kodster28 closed this Jan 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants