Repository navigation
Conversation
added 2 commits
November 13, 2026 15:47
…pacity, and sandbox organizations Adds a Large Data Loads page: how everyday traffic and large loads are processed, what a large load looks like from outside, the 503 response with Retry-After and BULK_CAPACITY_EXHAUSTED (whole and mixed requests), file imports that wait for capacity, and planning a migration. Adds the Sandbox Organizations page at the address the Integration Hub banner and the SANDBOX_LANE notice link to, for the new sandbox behaviour. Adds the 503 where retries are described (inbound getting started, interactive inbound closing rules and rate limits, replay) and cross-links from the overview and the configuration page.
… import Quotes the reworded 503 messages: the one for a request refused whole, the top-level message of a mixed request and the message on each refused event, and the new message of an import that gave up waiting. Shows a file import that waits for capacity through progress.waiting_for_capacity (since, retry_at, gives_up_at), with an example job, and drops the sentence that its progress simply does not advance.
This branch has not been deployed
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
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.
Replaces #182.
/integrations/integration-toolkit/large-data-loads): how migrations, full resyncs and large file imports are recognized and processed, what an integrator notices, and the one new response a client has to handle (503withRetry-AfterandBULK_CAPACITY_EXHAUSTED)./integrations/integration-toolkit/sandbox-organizations), rewritten from docs(integration-toolkit): sandbox organizations and the SANDBOX_LANE monitoring code #182 for the new behaviour: everyday traffic is handled as in production, large loads in a sandbox share a small capacity and run at a low rate. The Integration Hub banner and theSANDBOX_LANEnotice link to this address.inbound/getting-started.md: a "When to Retry" table for429and503.interactive-inbound.md:503added where retries are described; interactive events do not count towards the allowance and are never refused for lack of capacity.monitoring/investigating.md: a replay can also be answered with503.overview.md,configuration.md: cross-links.monitoring/codes.mdis generated and is not changed here.Do not merge before the feature is live. The pages describe behaviour that is not deployed yet, and two details will still change before then: the wording of the
BULK_CAPACITY_EXHAUSTEDmessage in the examples, and how a waiting file import shows in the API.