Scheduled automations

An automation is a request that runs by itself at the time you schedule. You write the request the way you would write in a conversation, choose which agent it runs with and how often — and Elyra executes it, keeping what happened for you to read later.

It is for the repeated work that does not need your presence: reviewing what opened, summarizing what changed, triaging what arrived.

Where to find it

In the corner menu of the window there is the Automations entry. The screen has two groups:

Group	What it is
Your routines	The automations created here in Elyra
External hosts	Jobs that belong to another system; see Automations from external hosts

What the list shows

Each routine reports:

• the name and the lifecycle state — enabled, paused, running, never executed, with error;
• the schedule, in readable form;
• the next execution, when it exists (“next in 3 h”, “next now”);
• the project it works in, and the agent it uses.

Opening a routine shows the detail:

Field	What it says
Schedule	The schedule in readable form
Agent	The agent that executes
Source	Where the task comes from, when the automation fetches work from a source
Session	Whether the runs reuse a session or start from scratch
Grace	How much delay still counts as “on time”
Precheck	The command that decides whether that run should happen
Last run	When the last execution was
Tokens	The accumulated consumption

And the actions: Run Now (run now), Edit automation, Delete automation and the pause/resume switch.

What an automation is, and what it is not

• It executes an agent, not a script. The request is natural-language text, and the agent decides how to fulfill it — with the tools and the permissions it has.
• It keeps history. Each run is recorded with status, workspace, spend and tokens.
• It does not replace supervision. What it does happens without you watching; read the history before trusting it with anything sensitive.
• It works in a project. The routine belongs to a project, and it is in that project’s repository that the work happens.

Pausing is not deleting

The routine’s switch pauses and resumes. Pausing stops the executions and keeps everything: the request, the schedule and the history. It is what you want most of the time — to stop without losing anything.

Deleting is another operation, and it is destructive.

Scope and limits

• The screen lists the installation’s automations, with the external jobs in a separate group.
• One automation action at a time. While an operation is in progress, the screen warns that another one is still running, instead of firing two on top of the same state.
• A nonexistent id fails, instead of returning an empty automation.

Next steps

• Creating an automation
• Runs and history
• Agent notifications