Scheduled job (cron)
A workflow or task configured to run automatically on a fixed time schedule, such as every hour, nightly, or on a specific day.
In more detail
A scheduled job runs on a clock rather than in response to an event: every hour, every night, every Monday. The name cron comes from the long-standing scheduling utility, and the pattern fits recurring work that is naturally periodic, a nightly reconciliation, a weekly report, a daily sync.
Scheduling is also the fallback for systems that do not emit events. If a source cannot push a webhook when something changes, a scheduled job can poll it periodically instead. The trade-off is latency and some wasted runs when nothing has changed, which is why event triggers are preferred where they are available.
Where this shows up at Ceven
Ceven workflows can run on a schedule for the processes that are naturally recurring or that depend on a system with no event feed. You describe when it should run as part of describing the outcome, and each scheduled run is a first-class execution recorded in the audit trail like any other.