Understand workforce rota cron processing

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 v1.3.0 after_cron_run hook, 15-minute throttle, due one-time queue and weekly target processing.

Before you start

• Access to Admin Area → Setup → Cron Job / Human Resources → Workforce Rota & Notifications.
• The Human Resource Management: View capability or administrator access.
• The correct employee, record, period or authorised evidence.

Follow these steps

1. Make sure the host application cron runs normally.
2. Verify all required notification and rota tables exist.
3. Wait until a scheduled one-time date/time or configured weekly day/time.
4. Run cron.
5. Check Notification Automation logs and rota Delivery/Audit logs.

What the module checks

• The module does not create a server cron job; it hooks after the host application cron.
• A setting prevents another module automation run within 900 seconds.
• Notification scheduler scan and up to 50 queue items run first; rota due distributions run afterwards.
• One-time due query is limited to 50 rows per run.

What happens next

The module saves the permitted change and records the resulting status, version, delivery or synchronisation evidence. Reopen the relevant register and verify it.

Troubleshooting

• If the control is missing, confirm the required HRM permission and module version 1.3.0.
• If saving fails, correct the exact field or state named in the validation message.
• If an email/automation is missing, review the module delivery/audit log and host cron/mail settings.

Related guides