Scheduling
Schedule Edilitics Transform pipelines to run once, daily, or on custom cron expressions. Pause, resume, or edit schedules anytime with timezone-awareness.
Every Transform pipeline has a schedule configured at save time. The schedule controls when the pipeline runs automatically. It can be changed, paused, and resumed at any time without rebuilding the pipeline.
Schedule options
| Option | What it does |
|---|---|
| Once | Triggers a single run immediately on save. While it has no recurring schedule, it can be manually re-triggered from the dashboard at any time. |
| Daily | Runs once per day at a specific time (HH:mm) of your choice in your account timezone. |
| Custom cron | Supports standard 5-part cron expressions (minute, hour, day of month, month, day of week) for precise automation. |
Recurring schedules (Daily and Custom cron) require a plan that supports auto-update intervals for the Transform module. If your plan does not support the selected interval, the save is rejected with a clear error.
Minimum cron interval by plan
The minimum interval you can set in a custom cron expression depends on your plan. Expressions that fire more frequently than the limit are rejected on save.
| Plan | Minimum cron interval |
|---|---|
| Individual Launch | Every 12 hours |
| Individual Scale | Every 6 hours |
| Individual Pinnacle | Every 1 hour |
| Team Launch | Every 6 hours |
| Team Scale | Every 3 hours |
| Team Pinnacle | Every 1 hour |
| Enterprise | Unrestricted |
The Daily schedule always fires at your chosen time in your account timezone regardless of plan. The minimum interval limit only applies to custom cron expressions.
Timezone
Schedules run in your account's configured timezone. When you set a Daily schedule, midnight means midnight in your timezone - not UTC. Custom cron expressions are also evaluated against your account timezone.
The timezone is stored on your account profile. If no timezone is set, schedules default to UTC.
Changing the schedule after creation
The schedule can be changed at any time from the pipeline dashboard without rebuilding or re-saving the operation sequence.
Choose a new schedule option: Once, Daily, or a custom cron expression.
When the schedule changes, the pipeline is not paused and the operation sequence is unchanged. The next run executes at the first interval of the new schedule.
Manual triggering
Regardless of the configured schedule, any pipeline can be executed immediately using the Trigger button on the pipeline card or in the settings panel.
- On-Demand Execution: Manually triggering a run does not affect the recurring schedule.
- Bypass Pause: You can trigger a run even if the pipeline is currently Paused. This is useful for testing changes before resuming the automation.
- Once Pipelines: For pipelines set to the "Once" schedule, the Trigger button is the primary way to re-run the pipeline without changing its configuration.
Every manual trigger is logged in Run History as a user_action, providing a clear audit trail of who initiated the execution.
Pause and resume
Any pipeline with a recurring schedule (Daily or Custom cron) can be paused from the dashboard. Pausing stops all future scheduled runs without deleting the pipeline or its configuration.
To pause: Click the pause control on the pipeline card or in the pipeline settings.
To resume: Click resume. Before resuming, Edilitics checks your compute balance. Resume is blocked if the balance is too low to cover a projected run - you'll see a clear error with a link to top up compute.
Once-schedule pipelines cannot be paused or resumed - they have no recurring schedule to suspend.
How runs are tracked after scheduling
After each completed run, the pipeline card shows:
- Last run - timestamp of when the most recent run ended
- Next run - the next scheduled execution time, calculated from the cron expression
Both are displayed in your account timezone.
The full execution record for each run - status, duration, phase logs, DQ scores - is available in Run History.
Frequently Asked Questions
Next steps
Run History
Track run status, phase logs, DQ scores, and execution metrics for every pipeline run.
Compute and Billing
Understand how compute is metered and what happens when the balance runs low.
Transform overview
Back to the Transform module overview.
Need help? Email support@edilitics.com with your workspace, job ID, and context. We reply within one business day.
Last updated on
Hybrid Pipelines
Combine no-code operations and Python Polars scripts in a single pipeline. Each step passes its output to the next regardless of type.
Run History
View run status, phase logs, DQ scores, row counts, and execution time for every Transform pipeline. Quickly diagnose pipeline failures by the exact phase.