Skip to content

fix(gastown): rollback agent to idle on dispatch container start failure #2000

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jrf0110 wants to merge 2 commits into from
+5 −5
Closed

fix(gastown): rollback agent to idle on dispatch container start failure #2000

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3182407
fix(gastown): rollback agent to idle on dispatch container start failure
Apr 4, 2026
dd0ee04
WIP: container eviction save
Apr 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions cloudflare-gastown/src/dos/town/actions.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -558,15 +558,15 @@ export function applyAction(ctx: ApplyActionContext, action: Action): (() => Pro

const capturedAgentId = agentId;
return async () => {
// Best-effort dispatch. If it fails, the agent stays 'working'
// and the bead stays 'in_progress'. The reconciler detects the
// mismatch on the next tick (idle agent hooked to in_progress
// bead) and retries dispatch.
// Best-effort dispatch. If the container start fails, roll the
// agent back to 'idle' so the reconciler can retry on the next
// tick. The bead stays 'in_progress' — no transition needed.
await ctx.dispatchAgent(capturedAgentId, beadId, rigId).catch(err => {
Copy link
Copy Markdown
Contributor

@kilo-code-bot kilo-code-bot bot Apr 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: This only rolls back rejected dispatches

ctx.dispatchAgent() resolves false for normal startup failure paths in scheduling.dispatchAgent() (for example when startAgentInContainer() returns false or the rig lookup fails). In those cases this .catch() never runs, so the agent still stays working and the 90-second dead zone remains. Handle a falsy return here as well if the goal is to roll the agent back to idle on failed container starts.

console.warn(
`${LOG} dispatch_agent: container start failed for agent=${capturedAgentId} bead=${beadId}`,
`${LOG} dispatch_agent: container start failed for agent=${capturedAgentId} bead=${beadId}, rolling back to idle`,
err
);
agentOps.updateAgentStatus(sql, capturedAgentId, 'idle');
});
};
}
Expand Down