Hrm Automation & Rota Distribution Notifications · How-to guide

Troubleshoot a scheduled workforce rota not sent

Diagnose host cron, timing, target week, version, recipient and status conditions that prevent v1.3.0 distribution.

Audience: HR administrators and authorised managersPermission: Human Resource Management: ViewModule v1.3.0
Exact navigation Admin Area → Human Resources → Workforce Rota & Notifications
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 → Human Resources → Workforce Rota & Notifications.
  • The Human Resource Management: View capability or administrator access.
  • The correct employee, record, period or authorised evidence.

How to do it

  1. Confirm the rota status is Scheduled.
  2. For one-time send, confirm scheduled_send_at is in the past.
  3. For weekly send, confirm feature enabled, current ISO day/time reached and week starts next Monday.
  4. Confirm last_distributed_version is lower than version_no.
  5. Confirm the rota is not cancelled/archived.
  6. Confirm valid recipients and host mail settings.
  7. Run host cron and inspect logs.

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.