[codex] Fix workflow task claim timeout#723
Draft
j-s wants to merge 1 commit into
Draft
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
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
WorkerOptions.claim_timeout.$ClaimTimeoutbefore they can finish.Root Cause
Agent-backed workflows such as
agent_surface_synccan legitimately run for longer than 5 minutes while still being bounded by the agent turn timeout. The api-rs worker was still using the platform default task-claim window, so a valid workflow could be killed with$ClaimTimeoutbefore the agent turn finished or reported.Validation
cargo test -p centaur-workflowsRust API fmt, clippy, and testspassed.auto-research-centaur-v1and verified a manualagent_surface_syncrun completed without recent claim-timeout logs.CI Note
The
Publish Imagesmatrix fails on this fork PR because GitHub reportsSecret source: Noneand Depot returnspermission_denied: Invalid token. That is a fork-permission/publishing-token limitation, not a Rust build/test failure.