Process Hub · Notifications and delivery

Check notification delivery and missing messages

Follow a message from its event and published policy through recipient resolution and delivery.

On this page

Before you start

  • Have authorised access to Notification delivery and safe details of a test event: process, record/work reference, approximate time and intended profile recipient.

Information to give your administrator

  • Instance/profile, process and safe record/work reference.
  • Event and approximate time with timezone; expected channel and recipient role.
  • Visible delivery status and safe error/reference. Do not copy credentials or private notification content into a support request.

Follow these steps

Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.

  1. Confirm the right instance/profile and the actual business event. For a due reminder, inspect the work item’s real due date rather than queue colour.
  2. Open Workflows → Notifications and confirm an enabled published policy covers that event and process. Check the active version, not just a saved draft.
  3. Review recipient type and event context. Assigned user needs a resolvable assignment; a profile-role recipient needs valid membership. Check whether an overlapping policy/lifecycle assignment already produced a message.
    Notification operations view with a retryable failed outbox entry and delivery diagnostics.View full size ↗
    Inspect the outbox status and reference before retrying. Correct the underlying delivery problem and consider duplicate risk.
  4. Open Monitor → Notification delivery. Filter/find the relevant process/time/reference and inspect its safe status and failure detail. Queued means it still needs delivery; it does not prove an email or push was received.
  5. Check the intended recipient’s inbox, personal channel preferences, digest and quiet hours/timezone. For push, confirm the mobile sign-in/permission setup; for email, have the administrator check the configured sender/delivery service.
    Notification Settings showing Quiet Hours and per-event channel preferences.View full size ↗
    Review the active profile, permitted channels, delivery timing and quiet-hours timezone, then save your preferences.
  6. Correct the policy, user setup or provider/worker issue. Review existing delivery and duplicate risk before an authorised retry. Trigger a fresh controlled event to verify the repair.

Example investigation

A Quality reviewer expects an overdue email. The task has a due date; the policy is published; Notification delivery shows Email queued. That narrows the next check to worker/provider and recipient preferences. Rebuilding the process fields would not resolve a queued delivery.

What you should see

You can identify whether the missing message is caused by an absent event, inactive policy, unresolved recipient, delivery failure or personal delivery preference.

If something goes wrong

The policy preview looks correct but no delivery row exists

Check that a supported event happened after the policy was released and that recipient resolution succeeded. A preview is not a send operation.

In-app works but email/push does not

Check each selected channel independently, including preferences, provider configuration, device permissions and delivery status.

A grouped message omits other people’s work

Grouping is per resolved recipient and compatible batch/event settings. It should contain only that recipient’s permitted items.

Need a hand?

Contact your organisation’s Emplyr administrator using your usual internal support channel.

How to ask for help