Define named cron schedules that drive pipeline execution timing.
## Overview The Schedules page allows platform administrators and data engineers to define named, reusable cron schedules that control when pipelines execute. Schedules are independent objects that exist outside any single pipeline, enabling a single schedule to drive multiple pipelines and a single pipeline to be linked to multiple schedules. Beyond cron timing, each schedule carries configuration for timezone, retry behavior, and execution timeout. This centralized approach ensures consistent scheduling policies across the platform and eliminates the need to duplicate timing logic within individual pipeline definitions. ## Key Features - **Cron schedule definition.** Specify execution frequency using standard cron expressions (minute, hour, day of month, month, day of week). A human-readable preview of the next several run times confirms the intended cadence. - **Timezone configuration.** Set the timezone for cron evaluation so that schedules fire at the expected local time regardless of the server's system clock. All standard IANA timezone identifiers are supported. - **Retry and timeout policies.** Define how many times a failed execution should be retried, the delay between retries, and the maximum allowed execution duration. Exceeding the timeout marks the run as failed and triggers the retry policy. - **Enable/disable schedules.** Toggle a schedule between enabled and disabled states without deleting it. Disabling a schedule suspends all associated pipeline triggers while preserving the configuration for future reactivation. - **Manual trigger.** Fire an immediate, one-off execution of all pipelines linked to a schedule without waiting for the next cron window. Manual triggers respect the same retry and timeout policies as scheduled runs. ## Workflow 1. Open the Schedules page from the Workflow sidebar. 2. Click the add schedule button and provide a unique name. 3. Enter the cron expression and select the evaluation timezone. 4. Configure retry count, retry delay, and execution timeout. 5. Save and enable the schedule. 6. Navigate to the Pipelines page and associate one or more pipelines with the new schedule. 7. Use the manual trigger to test the schedule immediately. 8. Monitor resulting executions on the Executions page to verify timing and success.