Get Execution
rundeck.get_execution
ActionBusiness appsconnection required
Calls the Rundeck API with the connection's credentials.
Read one execution's status, timings and per-node result.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Rundeck
- Secret shape
- the API token, or {"api_token": "…"}
- Config it needs
- base_url, api_version, project
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
execution_id The execution to act on; rundeck.run_job emits it as 'id'. | number | Yes | — | ≥ 1 | 1234 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"execution_id": 1234
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The execution id, which every other execution node takes. | number | — |
status Where the execution stands: running, succeeded, failed, aborted. | string | — |
project The project the execution belongs to. | string | — |
executionType How it was started: user, scheduled or user-scheduled. | string | — |
user The Rundeck user the execution ran as. | string | — |
href The API URL of this execution. | string | — |
permalink The Rundeck web URL a person can open. | string | — |
date-started When the execution started, as Rundeck reports it. | any | — |
date-ended When the execution finished; absent while it is still running. | any | — |
description Rundeck's one-line description of what ran. | string | — |
argstring The option arguments the execution was started with. | string | — |
job The job that was run. | object | — |
job.id The job's UUID. | string | — |
job.name The job's name. | string | — |
job.group The job's group path within the project. | string | — |
successfulNodes The nodes the execution succeeded on. | array | — |
failedNodes The nodes the execution failed on. | array | — |
{
"argstring": "",
"date-ended": null,
"date-started": null,
"description": "",
"executionType": "",
"failedNodes": [],
"href": "",
"id": 0,
"job": {
"group": "",
"id": "",
"name": ""
},
"permalink": "",
"project": "",
"status": "",
"successfulNodes": [],
"user": ""
}Notes
- status is 'running' until the execution finishes, then succeeded, failed, aborted or timedout.
See Get Execution run in a workflow.
In a technical demo we add the Rundeck connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.