Troubleshooting: Notification Problems
Use this guide when email, in-app, SMS, mobile push, workflow, approval, RFQ, billing, or support notifications do not arrive.
Notification problems can come from user contact details, profile preferences, device settings, spam filters, workflow recipients, inactive users, wrong vendor contacts, or a notification not being configured for that event.
Some notifications are now sent as scheduled reminders or digests instead of one message per event. Examples include pending approval inbox summaries, overdue invoice digests, check-in/check-out approval reminders, low-stock reminders, procurement request approval reminders, unanswered RFQ reminders, overdue PO delivery reminders, quotation expiry reminders, workflow/integration failure digests, security/device login digests, tenant deletion reminders, and plan or billing risk reminders.
First Checks
- Confirm the user email, phone number, and profile details are correct.
- Check spam, junk, promotions, company quarantine, or blocked sender settings.
- Confirm the user is active and assigned to the relevant role, branch, warehouse, vendor, or workflow.
- Check app/device notification permissions for mobile push issues.
- Confirm the event actually sends notifications to that user or role.
- Ask organization admin to verify notification preferences and workflow recipients.
- For reminders or digests, check whether the cadence is daily, weekly, monthly, or a custom interval before assuming it is missing.
Notification Types
| Type | What To Check |
|---|---|
| Email spelling, spam, quarantine, active account, and allowed sender. | |
| SMS | Phone number, country code, mobile network, and organization SMS settings. |
| In-app | User role, task assignment, unread notifications, and current workspace. |
| Push | Device permission, app login, app version, and notification settings. |
| Workflow | Recipient rule, approver assignment, task owner, and workflow status. |
| Vendor | Vendor contact email, RFQ invitation, deadline, and supplier user status. |
| Reminder or digest | Email notification setting, reminder cadence, last expected run, and whether there are records that qualify for the reminder. |
Reminder Cadence
- Daily reminders normally run once per day when matching records exist.
- Weekly and monthly reminders wait for the configured interval before another email is queued.
- Custom cadence uses the number of days selected by the organization admin.
- A reminder may correctly send nothing when there are no pending approvals, overdue invoices, low-stock items, unanswered RFQs, billing risks, workflow failures, or security events to report.
Common Mistakes
- Expecting a notification for an event that does not notify that role.
- Using an outdated vendor or user email.
- Forgetting phone country code for SMS.
- Blocking browser or mobile push notifications.
- Assuming notification failure when the task is assigned to someone else.
- Expecting an immediate email for a digest that is intentionally batched.
When To Escalate
- Many users stop receiving the same notification type.
- Critical approval, billing, RFQ, or support notifications are missing.
- Contact details and preferences are correct but nothing arrives.
- Workflow notification goes to the wrong person repeatedly.
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.