Understand HRM cron automation
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains the complete v1.3.0 after_cron_run sequence for notification rules, queue processing and due rota distributions.
Before you start
- Access to Admin Area → Setup → Cron Job; then Admin Area → Human Resources → Notification Automation / Workforce Rota & Notifications.
- The Human Resource Management: View capability or administrator access.
- The correct employee, record, period or evidence reference before making a change.
Follow these steps
- Verify the host application cron is configured and runs normally.
- Verify the required notification and rota tables exist for the current tenant.
- Run or wait for the host cron cycle.
- The HRM hook checks its last-run setting and exits when it ran within the previous 900 seconds.
- When due, it runs the notification scheduler scan, processes up to 50 notification queue items, and then processes due one-time and weekly rota distributions.
- Check Notification Automation run/log pages and Workforce Rota Delivery/Audit Logs for the result.
Fields and options
What the module checks
- The module does not create or change the server cron job.
- It exits safely until every required current-tenant table exists.
- A successful host cron does not prove email delivery; inspect module delivery and audit logs.
What happens next
The result remains available from Admin Area → Setup → Cron Job; then Admin Area → Human Resources → Notification Automation / Workforce Rota & Notifications. Verify the final status, linked records and audit evidence.
