Done

Team runs awaiting finalization go to "done" without team_finalize_run, closing tickets with open PRs

From Rob ZappDone 12 hours agovia agent-mcp

Team runs that reach End and wait in awaiting-finalization change to "done" although no agent calls team_finalize_run or team_cancel_run. The linked ticket moves to done. In our project the pull requests were not merged yet, so the board showed finished work that was not on the main branch.

Seen on 2026-10-21, three times:

  • one run went to done about 3 h 38 min after it reached End;
  • two runs went to done 3 min and 48 min after End, at almost the same moment (20:18:39Z and 20:18:58Z).

The agent that drives landing confirmed it did not finalize these runs, and no ticket comment records a caller. This may relate to the fix for ticket b17bc8b8 (runs stuck in awaiting finalization).

Workaround today: after every "Team run done" mail we check the pull request state and move the ticket back to in review by hand.

AgentsRoom diagnostics

  • App version: 1.225.0
  • OS: darwin 27.2.0 (arm64)
  • Agent CLI: claude
  • App language: system

Expected behavior

A run in awaiting-finalization stays there until an agent or the user calls team_finalize_run or team_cancel_run, or the app asks the callback agent before it closes the run.

Actual behavior

The run becomes done and its ticket closes, with no recorded caller, minutes to hours after End.

Steps to reproduce

  1. Run a team on a ticket until every step reaches End (status awaiting-finalization). 2) Do not call team_finalize_run. 3) Within minutes to hours the callback agent gets 'Team run done' and the ticket shows done, while its PR is still open.

Replies

The team13 hours ago

Thanks for the precise timeline, it pointed us to the cause. The fix will be available in the next version.

Why it happened: a run waiting at End only turns done when someone clicks Finish run (desktop or phone), when an agent calls team_finalize_run, or when one of two inactivity options finishes it on its own: "Finish after inactivity" in the team settings, or "Close after inactivity" on a trigger. Your two runs that reached End 45 minutes apart and finished 19 seconds apart match one pass of that inactivity timer. Our refusal message for agents_close also suggested turning that option on, so one of your agents may have switched it on. A run finished that way closed its ticket like a manual Finish, and nothing recorded who had finished it.

What changes:

  • Every run now records who finished it (you, the phone, an agent, or the inactivity option): in the run timeline, in the callback mail and in backlog_get.
  • A run finished by an inactivity option no longer closes its ticket: it goes to In Review when your board has that column (Done otherwise), with a note on the ticket saying nobody checked the work, and the callback mail says so instead of "Nothing is left to do".
  • The agents_close refusal no longer suggests turning the option on.

Until then, you can check Team settings > Finish after inactivity on your teams and turn it off if you did not set it yourself.

If this still happens after the update, please reopen this ticket with as much detail as you can (a screenshot or a video helps a lot).

Up to 3 images, or paste one straight from your clipboard. Big screenshots are shrunk in your browser before they are sent.

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.225.0 (darwin arm64)