fix(sync-model-stats): extend AA retry budget#3089
Closed
kilo-code-bot[bot] wants to merge 1 commit intomainfrom
Closed
fix(sync-model-stats): extend AA retry budget#3089kilo-code-bot[bot] wants to merge 1 commit intomainfrom
kilo-code-bot[bot] wants to merge 1 commit intomainfrom
Conversation
…retries are exhausted
Contributor
Author
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 files)
Reviewed by gpt-5.5-2026-04-23 · 217,557 tokens |
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.
Summary
The
sync-model-statscron was reporting Artificial Analysis 500s to Sentry even when the AA API itself indicated transient retryable errors (e.g.Could not query the database for the schema cache. Retrying.). The previous retry budget of 10s only allowed a handful of attempts beforefetchWithBackoffreturned the failed response and the route surfaced it to Sentry.This bumps the AA fetch budget to 2s base / 120s max, so we only get a Sentry report once retries are truly exhausted.
Verification
N/A — config-only change to retry timing.
Visual Changes
N/A
Reviewer Notes
The cron runs periodically; a 120s upper bound for the AA fetch is well within Vercel cron limits and only kicks in on sustained 5xx/429 responses.