A8gent
GlossaryAutomation mechanics

What is cron trigger?

Also called: schedule trigger, cron job, scheduled workflow

A cron trigger starts a workflow on a fixed schedule - every ten minutes, every weekday at 8am - using the cron expression syntax that has described recurring jobs on Unix systems for decades.

Written by A8gent
Contents
  1. At a glance
  2. What a cron trigger is
  3. Reading a cron expression
  4. Timezones, overlap and drift
  5. Cost and what to schedule
  6. What you should know
  7. FAQ
  8. Related terms

At a glance

Category
Automation mechanics
Standard fields
Minute, hour, day of month, month, day of week
Common variation
Some platforms prepend a seconds field - check the dialect before copying
Day-of-month plus day-of-week
Combines as OR in standard cron, not AND
Timezone default
Often UTC - set it explicitly and avoid the 01:00-03:00 DST window
Cost
Every run is billed whether or not it finds work

What a cron trigger is

A cron trigger runs a workflow at fixed times rather than in response to an event. The name comes from cron, the Unix job scheduler, whose expression syntax has become the standard way to describe recurrence across almost every automation platform. Where a webhook answers "something happened", a schedule answers "it is time".

Most platforms offer both a friendly picker - every hour, every weekday at 9am - and a raw cron expression for anything the picker cannot express. The picker covers the majority of cases; the expression is there for "the first Monday of the month" and similar.

Reading a cron expression

The classic form has five fields, in order: minute, hour, day of month, month, day of week. An asterisk means every value. So 0 8 * * 1-5 is 8:00 on Monday to Friday, and */15 * * * * is every fifteen minutes. Several platforms add a sixth seconds field at the front, which is the most common reason a copied expression fires at the wrong time - check which dialect your platform uses before pasting from the internet.

The other classic trap is day-of-month combined with day-of-week. In standard cron, specifying both is an OR rather than an AND, so an expression intended as "the 1st, but only if it is a Monday" will fire on every 1st and every Monday. Where you need that logic, schedule generously and filter inside the workflow.

Timezones, overlap and drift

Three operational problems account for most scheduling incidents. Timezone: many platforms default to UTC, so a job set for 08:00 runs at 09:00 local in British Summer Time and 08:00 in winter. Set the workflow timezone explicitly, and avoid scheduling anything critical between 01:00 and 03:00, where daylight-saving transitions cause a run to be skipped or repeated.

Overlap: if a run takes longer than the interval, some platforms start a second run alongside it, which is how the same records get processed twice. Check whether your platform prevents concurrent runs, and if not, use a lock or an idempotency key. Drift: scheduled runs are not guaranteed to fire at the exact second, and on busy shared infrastructure they can be delayed by minutes, so never build logic that assumes the run happened precisely on the hour.

Cost and what to schedule

Every scheduled run consumes a billing unit whether or not there is work to do, so frequency is a direct cost line - see executions, tasks and operations. A five-minute schedule is roughly 8,640 runs a month. If it usually finds nothing, that is the argument for a webhook and an occasional reconciliation sweep instead - the full comparison is on polling vs webhook.

Schedules are the right tool for genuinely time-based work: the overnight report, the Monday morning digest, the daily reminder run, the hourly reconciliation. For those, cron is not a compromise - it is exactly the correct trigger.

What you should know

Design scheduled jobs to be re-runnable. Use a stored high-water mark rather than assuming yesterday's run succeeded, so that a missed night is caught up automatically rather than leaving a silent gap. Alert on a job that did not run, not only on one that errored - the silent non-run is far more common and much harder to notice.

Cron trigger FAQ

What is a cron trigger?

A trigger that starts a workflow on a fixed schedule rather than in response to an event, described with cron expression syntax. It is the right choice for genuinely time-based work like nightly reports, morning digests and hourly reconciliation sweeps.

How do I read a cron expression?

Five fields in order: minute, hour, day of month, month, day of week, with an asterisk meaning every value. So 0 8 * * 1-5 means 08:00 Monday to Friday. Some platforms add a seconds field at the front, which shifts everything and causes a lot of confusion.

Why did my scheduled workflow run at the wrong time?

Almost always timezone. Many platforms default to UTC, so a job set for 8am runs an hour off during daylight saving. Set the workflow timezone explicitly, and avoid scheduling critical jobs in the 01:00 to 03:00 window where DST transitions skip or repeat an hour.

What happens if a run takes longer than the interval?

Depending on the platform, a second run may start while the first is still going, and both process the same records. Check whether concurrent executions are prevented; if they are not, use a lock or an idempotency key so a doubled run does no damage.

How often should a scheduled workflow run?

As rarely as the business need allows, because every run is billed whether or not it finds anything. If you are scheduling frequently just to notice changes quickly, a webhook is the better mechanism, with a much less frequent scheduled sweep as a safety net.

How do I know if a scheduled job silently stopped?

Alert on absence, not only on errors. Have the job write a heartbeat timestamp and have a separate check notify you when that timestamp is older than expected. A job that never fired produces no error anywhere, so error alerting alone will never tell you.

Primary source

crontab(5) - Linux manual page

Checked August 2026. Anything priced or rate-limited moves, so verify against the source before you budget.

Want this built rather than explained?

Knowing what cron trigger means is one thing; having it running in your business is another. We scope one workflow at a time, quote a fixed price in writing after a free consult, build it, and hand it over with documentation you own.