Tighten dsbx action poll: 500ms initial wait, then 200ms until 2s, then 500ms.

[Fraggle]

Description

DustApiClient::poll_action_result now waits 500 ms after a 202 response before the first status request, polls every 200 ms for the first two seconds, then returns to 500 ms polling for longer-running actions. This removes the guaranteed premature GET while improving completion latency for warm tools without changing the 10-minute cap.

Tests

Added unit coverage for the fast-to-slow polling boundary in pending_poll_interval.

Risk

Low risk. The change only affects action-status polling cadence; the existing timeout and network-error limits remain unchanged. Rollback is safe by reverting the dust-sandbox change.

Deploy Plan

Deploy dust-sandbox. No SQL migrations or infrastructure changes are required.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Actions	Updated
playground	Ignored	Preview	Sep 21, 2026 12:55pm UTC
storybook	Ignored	Preview	Sep 21, 2026 12:55pm UTC

[Fraggle]

This change is part of the following stack:

• Lazy-load sandbox function invocation GCS blobs. #32767
  • Add: Timings informations for tool calls. #32768
    • Tighten dsbx action poll: 500ms initial wait, then 200ms until 2s, then 500ms. #32769 ◀
      • Stage MCP tool outputs in Redis and write GCS behind markAsSucceeded. #32770
        • Stage sandbox function invocation blobs in Redis; defer GCS on create and terminal. #32771
          • Add create/run phase server timings for sandbox MCP tool calls. #32772

_{Change managed by git-spice.}