Running things on time.
WHAT THE SCHEDULER PROVIDES
Triggering work on a defined schedule, reliably, without a server.
WHAT IT CAN TRIGGER
A web request to your service A message published to a topic A task queued
WHY IT IS BETTER THAN A SERVER RUNNING A SCHEDULER
No machine to patch, and no machine to fail silently.
WHAT TO CONFIGURE
The schedule The target Retry behaviour Time zone
WHY TIME ZONE MATTERS
A schedule defined in one zone runs at unexpected local times.
WHAT TO ENSURE IN THE TARGET
That it can be called only by the scheduler, not by anyone.
HOW
Authentication using a service identity.
WHAT TO MAKE THE WORK
Safe to run twice.
WHY
Retries happen.
WHAT TO PREVENT
Overlapping executions, where a run has not finished before the next.
WHAT TO LOG
That it ran, when, and the outcome.
WHAT TO ALERT ON
Failure, and the job not running at all.
WHY THAT SECOND ONE
A scheduled job silently ceasing is invisible for months.
