Skip to content
Automation5 min read

The jobs that close your month while you sleep

Absent detection, auto check-out, leave accrual, digests and the year-end rollover all run as scheduled jobs. Here is what runs, when, and why every one of them is safe to run twice.

The AttendifyDesk team

The work nobody wants to do by hand

Most of the pain in attendance administration is not the software — it is the list of small, repetitive jobs that someone has to remember. Mark yesterday's no-shows absent. Close out the people who forgot to check out. Credit this month's leave. Carry the balances across on 31 December.

In AttendifyDesk those are background jobs. They run on their own schedule, and the admin console shows what they did.

What runs, and when

Daily jobs keep the record current:

  • Absent detection, skipping weekends, holidays and approved leave
  • Long-absence escalation — managers on day one, HR on day three, payroll flag on day five
  • Auto check-out at the end of the shift for anyone who forgot
  • Alert-rule scan and the attendance insights scan
  • The daily digest email, birthday and anniversary emails, and scheduled announcements
  • People operations — probation to active, joining reminders — and delegation activation and expiry

And the ones with a longer clock

Monthly and yearly jobs handle the parts of the calendar that only come around occasionally:

  • Leave accrual on the 1st of each month
  • Attendance score recalculation and the leave-pattern scan
  • The data-retention purge
  • Carry-forward and expiry of leave balances on 31 December
  • Scheduled reports, delivered by email on Pro and above

Idempotent, or it does not ship

Every job listed above is idempotent: running it a second time produces the same result as running it once. Leave accrual never double-credits a balance on a re-run. Absent detection does not overwrite an approved leave day. Billing webhooks are signature-verified and safe to replay.

This sounds like an implementation detail, and it is the single most useful property the system has. It means a retry after a transient failure is boring. It means an operator can re-run yesterday's accrual at nine in the morning without first working out what it already did. A number that was right stays right.

What you actually see

In the morning the daily digest lands in the inbox, the notification centre carries anything that needs a decision, and the dashboards show a month that closed itself. The jobs are only interesting when they are missing.

Back to all posts

Ready to get your team started?

Create your workspace in minutes, then choose Basic or Pro when you are ready.