Runs
A run is a single execution of a workflow. It runs on the server. A closed tab, a page reload or a server restart does not end it.
Start a run
You start a run in one of these ways:
- in the tab Run of a published workflow that can be started by hand
- with Run once now on a workflow with the trigger Schedule
- as a test run in the builder
The trigger also starts runs by itself.
If more than eight runs are running at the same time, the others wait visibly in the queue. Runs started by hand get their turn before runs started automatically, such as runs from emails or a schedule. This also applies to a run whose approval you have just answered.
Follow a run
- Open Runs in the sidebar, or the section Runs on the overview of a workflow.
- Click the row of the run.
The timeline of the run opens as a panel over the workflow overview. You can share its address. As long as the run is running, new steps appear automatically.
The timeline shows the start and end of each step with duration and tokens. It also shows tool calls with arguments and response, context fields that were entered, branches, questions, approvals, errors, interruptions and the end. Steps are collapsed. A click on a step shows its tool calls.
Stop a run
Click Stop. The button is in the run panel of the tab Run and, during a test run, on the trigger card in the builder. In the builder, Restart also ends the current run. The run ends with the status Cancelled.
There is no stop button in Runs. You cannot stop another person's run, because you do not see it.
Resume an interrupted run
A run with the status Interrupted is not finished. For a temporary disruption, lowcloud resumes it by itself. Otherwise it waits for a person.
If the AI service is overloaded, disrupted or cannot be reached, lowcloud tries again after 1, 5 and 15 minutes. The panel then shows Interrupted, will be resumed automatically with a countdown and has no buttons. lowcloud retries a timeout once after 1 minute. If the step has tools that write without approval, the run instead waits for a person immediately, because something may already have happened when it broke off. A run is resumed automatically at most five times.
For other disruptions, the panel shows Run interrupted and names the reason. The reasons are invalid access, used-up credit, a used-up monthly limit, a missing account, exhausted automatic retries, or a server restart during a run started by hand.
- Open the run. The button Resume in Runs only opens it, it does not resume it.
- Click Resume run in the panel.
lowcloud first checks the credit of the workspace and the monthly limit of the person. The run continues from the last saved point.
If you do not want to resume the run, click Discard run and confirm with Yes, discard. The run then ends with the status Cancelled.
On the entry Runs in the sidebar, a yellow badge shows how many runs are waiting for a person. When you get an email about this is described under Approvals and questions.
Run statuses
| Status | Meaning |
|---|---|
| Waiting to start | The run is queued. Nothing has been executed yet. |
| Running | The run is being executed. |
| Waiting for a response | The run is stopped at an approval or a question. |
| Interrupted | A disruption stopped the run. It is resumed automatically or waits for a click. |
| Successful | The run completed. |
| Failed | The run ended with an error. It cannot be resumed. |
| Cancelled | A person ended the run: with Stop, Discard run or a rejection without a reason. |
| Skipped | The first step classified the event from the trigger as not its responsibility. This is not an error. |
A run fails when the agent declares the task impossible, a step reaches its pass limit, a promised context field stays empty, or an intermediate state cannot be saved. The timeline shows the reason in a red line. A banner on the workflow overview says that the last run failed.
For email workflows, Skipped is the most frequent outcome. In the section Runs of the workflow overview, such runs are hidden by default, and they do not count towards the success rate. In Runs in the sidebar, you find them via the filter Skipped.
A run can also end without having run, for example when the trigger was changed and an older event is no longer processed. The reason is then in the answer line of the run.
Runs list
Runs in the sidebar shows the latest runs across all workflows, newest first. The columns are status, workflow, input, time and duration. Below the workflow name are the run number and the version, for example #12 · v3, or Draft. A run through your own setup carries the badge You.
Above the list you filter by status and search by workflow or input. Only statuses that occur in the list appear as filters, each with a count.
The list shows at most 50 runs. Filters and search work only on these 50. There is no paging and no export. The complete retained history of a workflow is in the section Runs of its overview. There you filter by version and status.
Run result
Below the timeline of a finished run is what came out:
- Context: one line per field with the value and the step that entered it. For an empty field, the reason is shown. If fields stayed empty, a notice above the card leads to the affected step.
- Result: the answer of the run. Show raw text shows it as raw text.
- Questions about the run: a chat that answers questions about this run from the stored history. It changes nothing and gives no recommendation for a decision. It offers starter questions, for example Why did the agent act this way?
In the builder, Replay marks the course of the run step by step on the canvas. There you can also repeat a single step of a run with the current state of the canvas. This works for test runs and for runs of your setup. The trigger cannot be repeated this way.
Retention
lowcloud deletes runs according to these rules:
| Rule | Limit |
|---|---|
| Age of a run | 30 days |
| Age of a skipped run | 7 days |
| Runs per workflow | the newest 30 remain, skipped ones do not count |
Runs in which someone granted or rejected an approval are exempt from the age limit. The limit of 30 runs per workflow still applies to them. lowcloud never deletes runs that have not ended.
Usage and costs stay in the billing, even when a run is deleted. You cannot configure the retention. You cannot delete individual runs either. Only a lowcloud platform administrator can do that.
When an approval or question expires, lowcloud ends the run. The action of an expired approval is not executed. This also applies when the page Approvals shows "As long as it takes".
Dashboard
The Dashboard at the top of the sidebar shows spend, use and open items of the workspace.
| Tab | Content |
|---|---|
| Overview | The key figures Members, Usage and Credit left. Below them Open items with counts per workflow, for example open approvals and questions, stopped and failed runs. |
| Usage | Billed amounts in the chosen period, split into Workflows, including test runs, Chat, Build and Knowledge. |
| Agents | Per agent and workflow: use with the number of failures, people, spend and last use. |
| History | One entry per chat message sent and per run: time, person, agent or workflow, and for a run also the status. The tab shows no content. |
| Members | Per member: last active, runs, chats and spend. |
In a client workspace, the tab Prices is added.
You choose the period from fixed spans or as a range of your own in the calendar. It applies to the tabs Usage, Agents, History and Members. The Overview is not limited to a period. There is no export.
Permissions
Who sees and can answer a run depends on whose accounts it runs through. New runs are always runs of a personal setup or test runs. Runs through the accounts of the workspace exist only as old runs.
| Run | Visible and answerable for |
|---|---|
| Run of a personal setup | only the person whose accounts it runs through |
| Test run in the builder | only the person who started it |
| Old run through the workspace accounts, workflow visible to the team | every member of the workspace who sees the workflow |
| Old run through the workspace accounts, workflow private | only the author |
Other people's runs do not appear in Runs, in Approvals or as a run detail. You cannot delegate or forward an approval to another person. You see other people's runs only as numbers without content. Anyone who may build (the role admin, or the former role developer) sees them per person in the tab Setups of the workflow. Admins see them in the Dashboard.
Only admins open the Dashboard. lowcloud redirects everyone else to the workflow list. People with the role member do not see a credit amount. Instead, they see the card Your monthly limit with their own spend in the Settings.
Only someone who may build can repeat a step of a run.