Repository navigation
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully 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.
An agent call that hit a usage limit slept until the window reset. Switching the provider or the account during that sleep changed nothing: the build kept waiting, and it retried only once the old window turned. Now a switch wakes the wait, and the call retries at once on the new provider or account.
Workflow.waiton theagents.quotatopic, with the reset as its timeout. The reset is read off the latest usage scrape, as before. The step that reads the reset also records which credential hit the limit: the agent's model, its billing, and the email of the subscription it runs on.Agent.wake_quota_waitswakes every run that waits on that topic. A change to the execution defaults, an agent's harness, model, or billing override, a connected subscription, or a pasted token calls it after the change commits, so the woken run reads the new settings.The retry on another credential does not consult that credential's scrape first. The scrape is keyed by the Druks account, so after a Claude account switch on the same Druks account it still describes the old Claude account. The provider's own rejection is the limit that applies.
A pasted setup token names no email, so swapping one pasted token for another reads as the same account, and the call waits out the reset.
The quota wait records different steps, so a run waiting out a quota when this deploys fails on replay and needs a new start.