feat(amsg-server): configure generation retries per task - #89
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Interactive replies currently inherit scheduled tasks' minute-scale generation retries, so a failed model request can leave the caller waiting through the full backoff even when they need an immediate result.
Add
maxGenerationRetriesas a number or safe-task selector on all server factories. It applies before the final response batch is committed to outbox; committed responses retain delivery-only retries. Existing deployments keep their current defaults.onFireSettled.willRetryandfailureStageexpose the shared retry decision without requiring applications to mutate provider errors or infer terminal state from retry counts.Validation: full
npm run cipassed (1,327 tests); all 18 focused integration tests passed, including the additional Cloudflare factory test. Coverage includes HTTP 200 error bodies, 429/503, network and pre-fire failures, default scheduled retries, outbox-only redelivery, legacy UUID execution, invalid configuration, and cancellation races. Includes a Changeset for the existingnextrelease workflow.