Troubleshoot HRM v1.3.0 cron automation
Diagnose missing tables, throttle timing, host cron, mail or due-condition failures without creating a separate server job for the module.
Exact navigation Admin Area → Setup → Cron Job / Human Resources → HR Command Centre
Code-backed scope These instructions follow Human Resource Management v1.3.0. Use only controls visible to your permission level and confirm the saved record or audit entry after every action.
What you need before you start
- Access to Admin Area → Setup → Cron Job / Human Resources → HR Command Centre.
- The Human Resource Management: View capability or administrator access.
- The correct employee, record, period or authorised evidence.
How to do it
- Confirm the host CRM cron runs successfully.
- Check HR Command Centre database health for every notification and rota table.
- Check notification_scheduler_last_cron_at and allow 15 minutes between runs.
- Check due dates/times and active statuses.
- Check mail settings and recipient lists.
- Review application error log for the caught HRM cron exception.
What the module checks
- The action is permission-aware.
- Required values must pass the exact server-side validation.
- Verify the saved record and audit/log result.
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.
HR data safety Restrict identity, right-to-work, payroll, bank, health, disciplinary and document information to authorised staff. Do not place protected values in free-text notes, email recipients or screenshots.
Browse connected topics: hrm automation