Hooks & events
Hook reference: system.tick
Use a scheduler completion summary without treating queued counts as final delivery or settlement.
About 2 min read
On this page
Trigger and payload
After successful core tick work, emaila:tick queues system.tick with the current ISO timestamp and summary counters.
{
"at": "2026-10-21T00:00:00+00:00",
"renewal_invoices": 0,
"reminder_candidates": 0,
"mail_queued": 0
}
The timestamp and zero counts above are examples, not installation activity. The core records its own run/heartbeat separately.
Interpret counters correctly
renewal_invoices counts documents generated during that tick. reminder_candidates describes eligible reminder work. mail_queued counts outgoing messages queued, not accepted inbox deliveries. Zero may be the correct result when nothing is due. A successful tick does not prove registrar jobs, hosting automation, every addon handler or the queue worker completed.
Appropriate addon work
Use bounded periodic internal maintenance that respects the addon's permissions and its own durable lock. Handle worker delay and repeated timestamps conservatively. Do not run long unbounded scans or create another scheduler loop. Ignore this event when your addon has nothing due.
Limits and diagnostics
The event is queued and its dispatcher timeout is bounded. Do not use a tick as fresh product-licence authorization or payment evidence. Missing events may reflect migration/install locks, a failed tick, worker backlog, addon verification/rights or a handler failure. Inspect the actual scheduler/run/queue/module diagnostics before manually launching more workers or replaying actions.