docs: Add error handling and retry guidance for HTTP Ingest connector #2627
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds a new section documenting: - HTTP 400 responses for schema validation failures - HTTP 5XX responses during connector restarts - Recommended retry strategy with exponential backoff This addresses a common customer question about occasional 500 errors during connector restarts. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Context
This addresses a recurring customer question about occasional 500 errors during connector restarts. Recent example: https://estuary-dev.slack.com/archives/C06R0CVD0KZ/p1768528893641379
Test plan
🤖 Generated with Claude Code