Automation and Jobs
Build multi-step maintenance workflows, schedule them with cron expressions, and review their run history.
#31.1Creating a workflow
+ in the left header, give it a Workflow Name, Create. New workflows start disabled with a daily-at-midnight schedule (0 0 * * *) and no steps.
The left list shows each workflow with a status dot (green = enabled), its schedule, and the outcome badge of its last run.
#31.2The workflow header
- Schedule with a pencil to edit it.
- Last run and total runs.
- Enabled / Disabled toggle button.
- Run Now — executes immediately using the active connection.
- 🗑 — deletes the workflow (with confirmation).
#31.3Steps
Add Step picks a type and an optional custom name. Six step types:
| Type | Configuration |
|---|---|
| Execute Script | A SQL / PL/SQL script to run. |
| Schema Compare | A Source Schema and a Target Schema. |
| Export Data | None — uses the active connection’s defaults. |
| Health Check | None. |
| Generate Report | None. |
| Email Notify | Recipient Emails (comma-separated) and a Message Template, which may include {WorkflowName} and {Status}. |
Steps are numbered and executed in order. Drag the grip handle to reorder them; the ⚙ button opens the step’s configuration; the 🗑 button removes it.
#31.4Scheduling
The Configure Schedule dialog takes a standard five-field cron expression, with a quick reference:
| Expression | Meaning |
|---|---|
* * * * * | Every minute |
0 * * * * | Hourly |
0 0 * * * | Daily at midnight |
0 0 * * 0 | Weekly on Sunday |
A workflow only runs on its schedule while it is Enabled and the application is running. Automation is an application feature, not a database job.
#31.5Execution history
The right column lists the last ten runs, newest first: a status icon (success / running / failed), the start time, the duration, and the run’s log output in a scrollable block.