Running now and reading the history
Trigger an immediate run and read what each run did: completed actions, skipped runs and runs that did not happen.
Run now
In the automation’s details, open More actions (the three dots) and choose Run now. The run is queued at once, and the screen says “Run sent to the queue.”
That notice is not the result. It says the run started. The outcome comes in the history.
When Run now is not available, the item itself says why (the automation turned off, or an operation in progress, for example).
From the command line:
elyra automations run <id>elyra automations runs --id <id> --jsonThe first command returns as soon as the run is queued, with the initial status. The second shows the
history: read status and error of the first item.
The history
The History section of the details has one row per run, grouped by day, with the time, the status and the reason it fired:

| What appears | What it means |
|---|---|
| Queued, Starting, Running | The run has not finished yet |
| Completed | The whole chain ran |
| Failed | An action failed. The row says “Failed at action N · type” |
| Skipped by the pre-check | The pre-check did not exit with code 0 (or ran out of time) |
| Not run | The run did not happen. The reason comes right below |
“X of N actions”
An automation with several actions shows “2 of 3 actions”: how many ran up to that point, out of how many were configured. If you edit the automation later, the old history keeps the total that applied at the time. Under Show details, each action appears as completed, failed or did not run (the ones after the first failure, which the chain never got to run).

There is also Open run, which takes you to the terminal or workspace of that run when they still exist, and Run again.
Why a run was “not run”
| Reason in the history | What happened |
|---|---|
| Elyra was unavailable at the time this run was scheduled (“Not run — Elyra was closed”) | Elyra was closed when the time arrived. Automations do not run while Elyra is closed, and missed runs are not run later. The automation’s details say how many runs were left behind |
| Not run: trigger limit | The trigger fired again within 30 seconds; Elyra runs at most one run every 30 seconds |
| Not run: event queue full | More than 50 events arrived while Elyra was starting; the extra ones were discarded |
| Not run: target unavailable | The automation’s workspace, project or SSH host was not available |
| Not run: the agent needs a login | The agent needs a login. Sign in to it once in the terminal and the next run continues on its own |
| entrega recusada: assinatura inválida (shown in Portuguese) | A webhook call arrived with the wrong secret |
A skipped run (pre-check) or a not run run is a result, not an Elyra error: the history exists precisely so you can see that the automation decided not to run, and why.
Filters
In the list of automations, All, On, Off and Need attention filter by state, and the search
filters by name. From the command line, elyra automations runs without --id lists the general history,
and with --id <id> only one automation’s.
Using this in practice
- After creating an automation, run it once now. A manual run shows whether the request is clear and whether the environment responds, before waiting for the trigger.
- Read the status, not “sent to the queue”.
- Read the reason when it fails or does not run. The history keeps the why.
- Check the consumption. Accumulated tokens and cost are how you notice an automation that is running more than it should.
Scope and limits
- The initial status is not the outcome. Treating the immediate answer as a result is the mistake this page exists to avoid.
- The history has a limit. Do not treat the list as the complete record of every run to date.
- Deleting the automation deletes its history.

