Approvers are not receiving Oracle Fusion approval notifications. Invoices sit unapproved for days because nobody knew they were waiting. Purchase orders stall in the approval chain. Expense reports pile up. The worklist shows pending approvals, but the email notifications that are supposed to alert approvers never arrive. This is one of the most disruptive post-go-live issues I see in Oracle Fusion implementations, because it silently breaks every business process that depends on timely approvals.

The notification system in Oracle Fusion involves multiple layers—BPM workflow engine, notification service, email delivery channel, and user preferences. A failure at any layer produces the same symptom: the approver never gets the email. Here is how to systematically diagnose which layer is broken.

Layer 1: BPM Workflow — Is the Approval Task Being Created?

Before investigating email delivery, confirm that the approval task is actually being created by the BPM (Business Process Management) workflow engine. The workflow must fire correctly before any notification can be sent.

How to check

  1. Navigate to the BPM Worklist application: Navigator > Tools > BPM Worklist (or search for “Worklist” in the Navigator).
  2. Log in as an administrator and search for the approval task. Filter by the transaction type (e.g., AP Invoice Approval, PO Approval) and the date range.
  3. If the task appears in the worklist with the correct approver assigned, the BPM workflow is working. The problem is downstream in the notification or email layer.
  4. If the task does not appear, the workflow is not firing. This means the approval rule is not triggering for this transaction.

Common BPM workflow issues

  • Approval rule not matching. Oracle Fusion approval rules use conditions (amount thresholds, transaction types, business units) to determine whether a transaction requires approval and who the approver is. If no rule matches the transaction, no approval task is created and no notification is sent. Review the approval rules in Setup and Maintenance > Manage Approval Rules for the relevant transaction type.
  • Approver assignment returning empty. The rule matches, but the approver assignment returns no one. This happens when the supervisory hierarchy is incomplete (the submitter has no supervisor in HCM), when a position-based rule references an unfilled position, or when a custom approval group is empty.
  • Workflow version mismatch. After an Oracle Cloud quarterly update, custom workflow modifications may become incompatible with the new version of the seeded workflow. The workflow errors silently, and no task is created. Check for BPM fault instances in the SOA console.

Layer 2: Notification Service — Is the Notification Being Generated?

Once the BPM task is created, Oracle Fusion’s notification service generates the actual notification message. This is where the notification template is applied and the delivery channel is determined.

How to check

  1. In the BPM Worklist, open the specific approval task and check its history. Look for a “Notification Sent” event in the task history. If it appears, the notification service generated the message.
  2. If there is no “Notification Sent” event, the notification service is not generating messages for this task type.

Common notification service issues

  • Notification preference set to “Do Not Send.” Each user has notification preferences in Oracle Fusion. If the approver’s preference for the relevant notification category is set to “Do Not Send” or “Worklist Only,” no email will be generated. Check the user’s notification preferences: Navigator > Preferences > Notifications (or the administrator can check via Manage User Notification Preferences in Setup).
  • Notification template disabled or missing. Oracle Fusion uses notification templates to format the email content. If the template for the relevant approval type was disabled during customization or is missing after an update, the notification service cannot generate the message.
  • Channel configuration issue. The notification service needs to know which channel to use (email, in-app bell notification, or both). If the email channel is not configured or is disabled at the system level, no email notifications will be sent for any approval type.

Layer 3: Email Delivery — Is the Email Actually Being Sent?

If the notification is being generated but the approver is not receiving the email, the problem is in the email delivery layer.

Common email delivery issues

  • No work email on the user record. Oracle Fusion sends approval notifications to the work email address on the user’s person record in HCM. If the work email field is blank or contains an invalid address, the notification has nowhere to go. This is surprisingly common for newly provisioned users or users migrated from a legacy system where email addresses were not mapped correctly.
  • Email going to spam or being blocked. Corporate email filters may block or quarantine Oracle Fusion notification emails. The sending domain for Oracle Cloud SaaS notifications needs to be whitelisted in the organization’s email security configuration. Check with the email administrator whether oracle.com or the Oracle Cloud notification domain is being filtered.
  • SMTP relay issues (for on-premises or hybrid deployments). If the organization uses a custom SMTP relay for Oracle Fusion notifications, verify that the relay is operational and that Oracle Fusion’s outbound email configuration points to the correct SMTP server and port.
  • Notification mailer service down. Oracle Cloud manages the notification mailer service, but occasionally it experiences delays or outages. If multiple users across the organization are not receiving notifications simultaneously, check Oracle Cloud status for any ongoing service issues.

Layer 4: Approval Rule Configuration Deep Dive

If notifications work for some transaction types but not others, the issue is almost certainly in the approval rule configuration for the failing transaction type.

Step-by-step rule review

  1. Navigate to Setup and Maintenance > search for “Manage Approval Rules” or “Manage Task Configurations” for the relevant module.
  2. Open the rule set for the transaction type (e.g., “Invoice Approval” for AP, “Purchase Order Approval” for Procurement).
  3. Check the rule conditions. Verify that the conditions match the transactions that are not generating notifications. Common misconfigurations include amount thresholds that exclude certain transactions, business unit conditions that do not cover all business units, or category filters that are too restrictive.
  4. Check the approver assignment. Verify that the approver type (supervisory, position-based, approval group) is correct and that the assignment resolves to an active user with a valid email address.
  5. Check the notification settings within the rule. Some rules have a “Notify” checkbox or a notification configuration that must be explicitly enabled.

Quick Diagnostic Checklist

  1. Does the approval task appear in the BPM Worklist? If no, fix the approval rule or workflow.
  2. Does the task history show “Notification Sent”? If no, check user notification preferences and the notification template.
  3. Does the approver have a valid work email in HCM? If no, update the person record.
  4. Are other notification emails being received from Oracle Fusion? If no, check the email channel configuration and corporate email filtering.
  5. Is the issue isolated to one approval type? If yes, review the specific approval rule configuration.

When to Get Expert Help

Notification issues that span multiple layers—a combination of workflow misconfiguration, incorrect approval rules, and email delivery problems—are difficult to untangle without deep Oracle Fusion BPM expertise. If approval workflows are stuck or notifications have been unreliable since go-live, a Stabilization Sprint can systematically audit and fix the entire notification chain across all approval types in 1–2 weeks.