Running a deployment and reading run history

Once a workflow is deployed in CloudRadial AutomationAI, you can run it and review every execution in History. This article covers running a deployment, the statuses and trigger types a run can have, and drilling into a run's steps. It is for all roles.

• Running a Deployment
• The History View
• Run Statuses
• Trigger Types
• Drilling Into Run Steps

Running a Deployment

A run executes the deployment's pinned published version. You start one with the Run action in the Designer, choosing the target deployment to launch. The work is queued rather than run on the spot: the deployment's runner picks it up on its next poll and reports progress back, so a run begins as pending and advances as the runner works. Runs also start on their own from a schedule or a webhook trigger.

The History View

Open History (/runs) to see every workflow execution across your workspace, newest first. Each row shows the workflow, status, trigger, the user who started it, the runner, start and completion times, duration, and step count. The view updates live as runs progress, so a run appears and its status changes without a manual refresh. You can sort and filter the columns and page through the history. Opening a run from the Runners dashboard or from a workflow scopes the view to that runner or workflow.

Run Statuses

A run carries one status as it moves through its lifecycle:

• Pending — queued, waiting for the runner to pick it up
• Running — the runner is executing the run's steps
• Succeeded — every step completed successfully
• Failed — a step errored and the run did not complete
• Timed out — a step exceeded its allowed time and the run was stopped

A run can also be cancelled. For what to do when a run fails or times out, see the article on troubleshooting a failed or timed-out run.

Trigger Types

The Trigger column shows how each run started:

• Scheduled — fired by a Routine on its cron cadence
• Manual — started by a person with the Run action
• Webhook — started by an inbound call to the workflow's webhook trigger

Drilling Into Run Steps

Click a run to open its detail, which lists the run's steps in order. Each step shows its language, its status, and its sections: the step's Output, its Log if one was captured, and its Error if it failed. The first step is often the synthetic trigger step, which shows the trigger payload — the manual or webhook JSON the run started with — rather than a runner result. An open run detail updates live as the runner reports each step.