Runs and Activity
A run is one execution of a workflow.
Activity is the place to see what happened: which workflow ran, which nodes completed, what paused, and what failed.
Run statuses
Common run statuses are:
| Status | Meaning |
|---|---|
queued | The run is waiting to start. |
running | The workflow is currently executing. |
awaiting_input | The workflow paused for a human step or reauthentication. |
completed | The workflow finished successfully. |
failed | A node failed and the run stopped. |
cancelled | The run was stopped before completion. |
Node states
Inside a run, each node also has a state.
A node may be pending, ready, running, paused, completed, failed, or skipped. Skipped usually means a condition did not activate that branch.
Human input
Human nodes pause a run when someone needs to review, decide, edit, or approve.
When you complete the human step, the workflow stores that final state as output for downstream nodes. For example, later steps can branch based on whether a reviewer chose approved or escalated.
Browser reauthentication
Browser integrations use logged-in sessions. Sometimes a website logs out, asks for MFA, or needs a fresh sign-in.
When that happens, Gondo can pause the run and ask you to reconnect or sign in again. After that, the workflow can continue with a fresh authenticated browser session.
Failures
A failed run should tell you which node failed and why.
The most common causes are:
- An integration is disconnected or missing permission.
- A file, record, board, sheet, or folder could not be found.
- A task instruction was too vague.
- A code node expected a field that was not present.
- A website changed or required login.
Use the failed node as the first clue. Most fixes are small: reconnect an integration, make instructions clearer, add a human review step, or adjust the expected schema.