Skip to main content
← Back to list
01Issue
BugShippedSwamp CLIPublic
Assigneesstack72

Relationships

#4830 client: an HTTP action refused as serve_not_leader with inFlight is retried and can run twice

Opened by stack72 · 11/17/2026· Shipped 11/18/2026

packages/client/http_transport.ts refusedBeforeActing treats any 503 with Retry-After as refused before acting, except outcome_unknown and still_working. A team follower's LeaderLink answers a forward that failed after it was sent with notLeaderResponse (src/serve/leader_link.ts): 503, code serve_not_leader, inFlight: true, and always Retry-After: 5. So the HTTP action transport retries an action the leader may already have run, for example when the leader dies mid-request, and the action can run twice. Expected: a reply carrying inFlight: true is treated as outcome unknown (outcomeUnknown), never retried blindly. Found while planning swamp-club#4811 (team rolling restart).

02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 6 MOREPR_LINKED+ 2 MORESESSION_SUMMARIZED

Shipped

11/18/2026, 2:55:57 AM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack7211/17/2026, 8:28:41 PM

Sign in to post a ripple.