Agentic Workflows
Running, scheduling and history
Run it now
Click Run in the editor's top bar. The workflow is saved, then a panel shows each step as it runs — its status, how long it took and what it produced — with the total cost at the top. Blocks turn green or red on the canvas.
Two switches beside Run change how it runs:
| Background | The run keeps going if you close the tab, and starts within a minute. Use it for anything long: a run you watch stops after about 24 seconds, a background run after about 2 minutes. |
|---|---|
| Notify | Emails you when the run finishes, with its result, or when it stops for approval. |
Opening a workflow that is running right now — on its schedule, or in the background — follows the run without being asked.
Put it on a schedule
- Add a Schedule block and choose When it runs: Every so often, Every day, Every week or Advanced (cron).
- Set the status at the top to Active.
- Click Save.
The top bar shows when it runs next. Day and week times are in your own timezone; a cron expression is in UTC. A Draft or Paused workflow never runs on its schedule, though Run still works.
Approving a Human checkpoint
A run that reaches a Human checkpoint stops there, and its status is Waiting for approval.
- Open the workflow. A run that is waiting opens by itself; otherwise click History and open it.
- Read what the box at the top asks you to check.
- Add a note if you want one, then click Approve and continue or Reject.
Approved, the run carries on from the checkpoint within a minute, in the background, and the panel follows it. Rejected, it ends, and History lists it as Rejected with your note.
| Who can approve | Anyone who can run the workflow, unless the block's Who can approve is set to Account owners and admins only. |
|---|---|
| Who is told | A scheduled or background run that stops at a checkpoint emails the workflow's owner, or the person who ticked Notify. A run you are watching shows the box straight away. |
| How long it waits | 7 days. After that, the run stops. |
A checkpoint cannot sit inside a Parallel branch. Put it before the Parallel block, or after the branches meet. A Test chat that reaches a checkpoint cannot answer in the chat; approve it from History, and its answer is recorded there.
History and versions
History lists the last 50 runs — how each started, its status and summary. Click one to see every step. Versions lists saved versions of the workflow (every save makes one; the last 20 are kept), each with Restore.
What it costs
Each AI step is charged to your account's credit and shown in Observability under Agentic workflows. A single run stops if it spends $5.00.
If something goes wrong
| Failed at "…": … | The step named failed, with the reason. The steps after it did not run. |
|---|---|
| Stopped at the time budget — some steps did not run. | The run took longer than a watched run is allowed. Tick Background and run it again. |
| Stopped at the spend limit ($5.00). | The run reached $5.00 of AI spend. |
| Stopped at the step limit (100 steps). | The run took 100 steps. Look for a loop of blocks that leads back on itself. |
| A Human checkpoint cannot sit inside a Parallel branch. | Move the checkpoint before the Parallel block, or after the branches meet. |
| Nobody approved or rejected it within 7 days, so it stopped at the Human checkpoint. | Run it again when someone is available to decide. |
| This run stopped before it finished - it was interrupted rather than completed. Run it again. | The run was cut off — for example, the tab was closed during a watched run. Nothing is retried for you. |
| This account is out of AI credit. | The account owner, or an admin with billing access, adds credit in Account → Billing; the message names the owner. A scheduled workflow skips its runs until then, emails its owner once, and carries on by itself when credit is added. |
| Slack isn't connected to this account | A Send Slack step needs Slack connected. Connections |
Signed in to VeraGen? Press Guide me on any screen for a walkthrough, or ask Odin.