Skip to content

Increase intent polling timeout to 210s#360

Merged
kopy-kat merged 1 commit intomainfrom
kopy-kat/poll-timeout-210s
Feb 26, 2026
Merged

Increase intent polling timeout to 210s#360
kopy-kat merged 1 commit intomainfrom
kopy-kat/poll-timeout-210s

Conversation

@kopy-kat
Copy link
Member

Summary

  • Bumps POLL_MAX_WAIT_MS from 180s to 210s in waitForExecution()
  • The orchestrator's worst-case intent expiry marking is exactly 180s (120s fill deadline + 30s expiration buffer + 30s check interval), creating a race condition where the SDK could time out before observing a terminal status
  • 210s gives a 30s buffer so the SDK always sees the final expired/failed state before giving up

Test plan

  • Verify waitForExecution() polls for up to 210s before throwing IntentStatusTimeoutError
  • Confirm normal intent flows (fill, claim) still resolve well within the new timeout

🤖 Generated with Claude Code

The orchestrator's worst-case intent expiry is 180s (120s fill deadline
+ 30s expiration buffer + 30s check interval). With POLL_MAX_WAIT_MS
at 180s the SDK could time out before seeing a terminal status. Bumping
to 210s gives a 30s buffer to guarantee the SDK always observes the
final expired/failed state.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@kopy-kat kopy-kat merged commit 71f11da into main Feb 26, 2026
5 checks passed
@kopy-kat kopy-kat deleted the kopy-kat/poll-timeout-210s branch February 26, 2026 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants