Several things happen on a schedule rather than when somebody clicks. They are all listed, all optional, and all can be run as a dry run first.
1. Available jobs
| Job | What it does | Sends email |
|---|---|---|
| Timesheet reminders | Nudges people who have missing days | Yes |
| Approval reminders | Nudges approvers with a stale queue | Yes |
| Leave auto-decision | Settles leave pending too long | Yes |
| Scheduled reports | Sends the recurring summaries you configured | Yes |
| Approval history cleanup | Deletes audit rows past their retention window | No |
| Data retention sweep | Deletes leave, timesheet and suppression data past their windows | No |
| Unlock expiry cleanup | Marks granted unlocks expired once their window passes | No |
2. Enabling a job
Each job has a cadence and, where relevant, a day. Enable only what you want; nothing runs unless you turn it on.
3. Choosing the audience
Reminder jobs let you choose who they reach — everyone, or a narrower set. A reminder that goes to people it does not concern is a reminder people learn to ignore.
4. The bulk-email cost gate
Jobs that fan email out to a derived list of people are gated behind using your own SES account. Sending to a whole site on the built-in sender is a cost we are not able to carry on your behalf, and a surprise bill for us is a surprise outage for you.
Jobs that send nothing, or send only to a short list you typed yourself, are not gated.
5. Dry runs and history
Dry run reports what a job would do and changes nothing. Use it before enabling anything that deletes or emails.
Run history shows what each job did and when, so an unexpected change has somewhere to be traced to.
