Schedules
Workflow clocks on Camel Quartz + Redis.
Portal Schedules lists workflow clocks Connect knows how to fire. The clock is Camel Quartz; Temporal holds the waiting graph. Multi-replica landings claim each fire in Redis so one tick starts one run.
Open PortalSources
| Source | What appears |
|---|---|
Workflow spec.cron / spec.schedule | Published workflow clocks |
schedules.cron file | Optional business CronJobs (this landing has none) |
File format:
# job-name schedule(UTC) description
example-nightly-job 0 2 * * * Nightly example batchRun now
Admins trigger a published schedule (POST /api/v1/ops/schedules/{id}/run). Run now is operator-initiated and does not take the Redis fire claim.
Next: Workflows