Repository navigation
T-22624 [CI] Wait for a SQL API query slot instead of failing on HTTP 429 - #65
Merged
Merged
Conversation
The read-back queries the team's SQL API connection as one user, and that user may run 4 logs queries at a time. Every job of this workflow, and of the other client repos' E2E workflows, polls as that user, so when enough jobs read back at once the connection answers HTTP 429 and the job fails although every line was delivered. ?wait=true queues the query for up to 60 s instead, and the curl timeout grows to 90 s to leave room for that. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
PetrHeinz
marked this pull request as ready for review
November 9, 2026 09:59
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.
The E2E read-back queries the team's SQL API connection as one user, and that user may run 4 logs queries at a time. Every job of this workflow polls as that user, and so do the E2E workflows of the other client repos, so when enough jobs read back at once the connection answers HTTP 429 (
You've reached the limit of 4 concurrent logs queries for user …) and the job fails although the client delivered every line. The logtail-js workflow alone runs 22 jobs in parallel and hit this on 2026-11-05 and 2026-11-06.The read-back now asks the SQL API to queue the query with
?wait=true, which waits up to 60 s for a slot instead of answering 429, and the curl timeout grows from 60 s to 90 s so a queued query keeps time to run.The
verify-logsaction is a byte-identical copy in every client repo, so the same change lands in each of them.🤖 Generated with Claude Code