Skip to Content
How-to guidesContinue a finished run

Continue a finished run

Pick a finished run up where it left off. The agent wrote a fix but skipped the tests, or the run timed out halfway through a migration: continue it with one instruction instead of starting over. The new run already holds the old run’s conversation, and your message is its first instruction. The old run does not change.

Before you start

  • Role: you may act on the run, for example because you started it.
  • The run has finished.
  • Available when your administrator enables runs and deputies.

Steps

  1. Open the finished run from Runs.
  2. In the header, click Continue….
  3. Read the note in the popover Continue this run. It says whether the files come across (“The files come across.”) or not (“The files do not come across.”). If the files are gone, the agent is told to clone the repository again.
  4. In Instruction for the agent, say what to do next, or what to do differently. For example “Keep going, but skip the tests.”
  5. Click Continue run. The keyboard shortcut is Ctrl+Enter or Cmd+Enter.

If a run ended because nobody answered its question, the run page tells you so and points to Continue run. Your instruction can carry the answer.

When a run cannot be continued, the header shows Can’t continue with the reason:

  • The run’s conversation is past its retention period.
  • The chain has been continued 10 times. “This would be number N in the chain; 10 is the limit.” shows before you send.
  • The run was already continued. The header shows Continued by the other run.

From the CLI

Run marshal runs continue with the run’s ID and your instruction:

marshal runs continue <run-id> --message "Keep going, but skip the tests." --follow

--message is required. It plays the role --task plays for marshal run. The command prints the new run’s ID and time budget. With --follow, it streams the new run until it ends and exits with an error code unless the run succeeded. With --json, it prints the new run as one JSON object, and continues_run_id holds the ID of the run you continued.

If the run cannot be continued, for example because it is still working, the command shows the reason and exits with an error code.

What you should see

  • The new run opens. Its header says it is a continuation of the earlier run.
  • The first thing it does is act on your instruction.
  • The old run now shows Continued by the new run. On the Details tab, a Chain panel lists the runs that belong together.

Next

Run a mission on a schedule or event: once the work runs the way you want, let the deputy start it on its own.

Answer a question from a runRun a mission on a schedule or event