Automation and AI
Workflow Executions
Live history of every workflow run — status, timing, per-step progress, and nested subagent runs.
A Workflow Execution is a live record of one run of a deployed Workflow Definition. The Executions page is where you watch runs happen and review what happened afterwards.
The runs list
Section titled “The runs list”The left-hand list shows every run, newest first. Selecting a run shows:
| Detail | What it shows |
|---|---|
| Workflow | Which Workflow Definition this run executed |
| Status | Where the run currently stands — see below |
| Revision | Which deployed version (e.g. “v3”) the run executed against |
| Trigger | What started it — Manual, Schedule, Webhook, Data change, or Chat |
| Started / Duration | When it started and how long it has taken (or took) |
| Steps | How many steps have completed, out of the total (when known) |
Run status
Section titled “Run status”| Status | Meaning |
|---|---|
| Pending | Admitted, about to start. |
| Running | In progress. |
| Completed | Finished successfully. |
| Failed | Stopped because of an error, or because it hit its step-limit (“ceiling reached”) — either way, shown as Failed with a short reason. |
| Cancelled | Stopped before finishing, not due to an error. |
A running or waiting run also shows an activity indicator — whether it’s actively working or momentarily parked (e.g. waiting on a subagent).
Nested runs
Section titled “Nested runs”A workflow step can spawn a subagent or a child sub-workflow. When it does, that child appears nested under its parent in a children tree, so you can drill into exactly which part of a larger run is in progress or where it failed — however deep the nesting goes.
Step trace
Section titled “Step trace”Selecting a run shows its steps in order, each with:
- Status — Running, Success, Failed, Cancelled, Skipped, or Pending
- Duration
- A short, human-readable summary of what happened
- The tool name, when the step called an external tool
For safety, only this short summary is shown — GreenVee deliberately doesn’t surface the raw underlying request/response data (which can contain sensitive values) in the trace.
Exporting a run
Section titled “Exporting a run”Use the Export menu on a selected run to download it as:
- JSON — the full structured record, useful for archiving or sharing with support
- AI digest — a compact, token-efficient summary meant for pasting into an AI conversation
Related pages
Section titled “Related pages”- AI Glossary — plain-English definition of Workflow Execution
- Workflow Definitions — building and deploying the workflow behind a run
- Workflow Triggers — what starts a run
- How Automation Runs — where executions fit in the bigger picture