Done

team_cancel_run on a run blocked by max cycles answers "cancelled" but leaves it blocked and the team locked

From BiTzaDone 1 week agovia agent-mcp

A team run in messaging mode stopped with status blocked ("Max cycles (3) reached on node <node>"). The orchestrating agent then called team_cancel_run({runId, reason}).

Observed:

the call returned ok: true, status "blocked", and the message "The run is cancelled and its temporary consoles are being torn down...";
the run's state stayed blocked and its box stayed in the sidebar;
teams_save (nodePatches on stepInstructions) on that team kept being refused with "... is currently running, so this definition is what governs the agents of that run ...";
per the docs, its ticket could not start a new run either (one live run per ticket).

Only the user's Dismiss on the run, done from the phone app, released it: the run's folder disappeared and the next teams_save was accepted at once.

The tool description says a run that already ended (done/cancelled/blocked) "is reported as such, not re-processed", but the returned message says it was cancelled, so the agent believes the run is gone. An agent working unattended at night cannot unblock the team or restart the ticket without waking the user.

AgentsRoom diagnostics

App version: 1.214.0
OS: darwin 27.0.0 (arm64)
Agent CLI: claude
App language: system

Expected behavior

team_cancel_run on a run blocked by max cycles ends it like Dismiss (the team becomes editable again and the ticket can start a new run), or refuses with a clear message that only the user can dismiss it.

Actual behavior

It returns ok: true with status "blocked" and a "run is cancelled" message; the run stays blocked, teams_save on its team stays refused, and the ticket cannot be restarted until the user dismisses the run in the app.

Steps to reproduce

A team in messaging mode with maxCycles 3. 2. Let a QA -> Dev loop block the run on max cycles. 3. From an agent, call team_cancel_run({runId, reason}). 4. Call teams_save with nodePatches on the same team: refused as running. 5. Dismiss the run in the app (phone or desktop): teams_save works right away.

Replies

The team1 week ago

Thanks for the very precise report. The cause: a run stopped by its max cycles is paused, not finished. It keeps its consoles so you can add cycles and resume it, and while it is in that state its team stays locked for agent edits. The cancel tool treated such a run as already finished, so it changed nothing while still answering "cancelled", and the team stayed locked until the run was dismissed by hand.

What changes: team_cancel_run now really ends a run stopped by its max cycles. Its consoles are closed, agents can edit the team again right away, and the ticket can start a new run. The run stays in the finished list as cancelled, with the reason the agent gave, so you can see in the morning what happened. When a run had already finished, the tool now says that nothing was changed instead of claiming it cancelled it, and team_finalize_run refuses a stopped run and points to the two ways out (cancel it, or add cycles). The fix will be in the next release.

If the problem is still there after this update, please reopen this ticket with as many details as possible (a screenshot or a video helps a lot).

The team1 week ago

Thanks: the bug is fixed and the fix ships in the next release. If it still happens after that, tell us and we will gladly take another look.

Sent automatically with your message

Your browser sent this along so the team can reproduce what you saw. Nothing here was typed by you.

Browser: AgentsRoom-MCP/1.214.0 (darwin arm64)