You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(serenity): retry transient upstream/network errors during a workspace status poll (LLMO-7418 external-review Finding 14)
Previously any error from transport.getWorkspaceStatus() — including a
transient Semrush 503 or a network blip — landed in the generic outer catch
and permanently failed the whole provisioning attempt with zero retries,
even though the worker already has a bounded self-requeue mechanism built
for exactly this "try again shortly" case.
Classify by error.status: SerenityTransportError with 429/500/502/503/504,
or any error with no status at all (a raw network-level failure), is now
treated as transient — the poll result falls through as if the workspace
were merely "not ready", routing through the EXISTING self-requeue ladder
(same backoff/depth cap, no new mechanism). Everything else (a permanent
4xx like an expired IMS token) keeps today's fail-fast behavior.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
0 commit comments