Skip to content

Run an Automation and read Runs

A Run starts a fresh Session with an Automation’s Instructions as its first message. It does not resume an existing Session.

  1. In your project’s navigation, open Automations and select an Automation.
  2. Select Run.
  3. For an Automation without a Schedule Trigger, the Run “name” on dialog opens. Use Find a ticket to search by title or ticket ID, then select a ticket.
  4. Select the button labelled with your ticket, such as Run on VLT-12.

A scheduled Automation runs at the project level instead, so Run starts a Board Session without asking for a ticket.

The Run starts without navigating away. Select Open session in the success notification to open its Session.

You can also run an Automation from a ticket’s Automations section or from Automations in its board card’s context menu. In the Ticket view, select an Automation to inspect its instructions, use Run on to override the model and reasoning for one Run, then select Run. The Automation armed for the ticket’s column appears first. The command palette also lists Automations you can run on the open ticket.

Automatic triggers controls automatic starts only. You can run an Automation by hand while it is off. A manual Run uses the Automation’s Runtime, unless you select a one-time override in the Ticket view.

Volli will not start another Automation Run on a ticket while an earlier Run is working or waiting for your answer. Answer or interrupt the earlier Run before starting another. For project-level Runs, this guard applies to earlier Runs of the same Automation in that project; different scheduled Automations can run together.

If a saved model is no longer available, inspect the Run’s Session for the failure and repair the model connection or Runtime. Volli does not silently replace a pinned model with another one.

Select an Automation to see Recent runs, then All runs for its full history. Rows are newest first. Each Run shows its launch-time Automation name, ticket ID when available, model and reasoning, start type, and time. Select a row to open its Session.

By hand includes manual Runs and deliberate column moves. Automatic includes scheduled Runs and Runs started by another agent. These labels record how the Run started, not the Automation’s current Trigger.

A missed scheduled time appears with Skipped and a reason. Select Run now to start one project-level Run; this does not replay every missed occurrence. See Schedule an Automation.

On the Automations page, select History to read combined Runs and skipped occurrences across the project. Use its All automations filter to narrow the list. History remains available after you delete an Automation; deleting its definition does not delete its past Runs or Sessions.