# Oracle EBS Workflow Mailer Troubleshooting Checklist (Log Location to Purge) > Source: https://netray.co/tools/oracle-ebs-workflow-mailer-troubleshooting-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A grouped checklist for EBS 12.1 and 12.2 when workflow notification emails stop going out, arrive late or responses are not processed. ## Category oracle ## Erp Oracle E-Business Suite ## Audience - Apps DBA - EBS system administrator - Workflow administrator ## Tool **Kind:** checklist **Groups:** #### 1. Service status **Items:** **Text:** In Administer Concurrent Managers, confirm Workflow Mailer Service and Workflow Agent Listener Service are running with actual = target **Critical:** true Query FND_SVC_COMPONENTS: COMPONENT_STATUS should be RUNNING for COMPONENT_NAME 'Workflow Notification Mailer' Check the mailer status and last error in Workflow Manager (Oracle Applications Manager) > Notification Mailers Confirm the Concurrent Managers themselves are up; service components run under them #### 2. Logs **Items:** **Text:** Find the mailer log: FNDCPGSC.txt in $APPLCSF/$APPLLOG on the concurrent node **Critical:** true Identify the right file from the Workflow Mailer Service process id in Administer Concurrent Managers Raise the mailer component Log Level parameter to statement level while reproducing, then set it back Look for SMTP or IMAP connection errors and Java exceptions near the time emails stopped #### 3. Outbound email **Items:** **Text:** Check the outbound SMTP server name and port, and that the concurrent node can reach it **Critical:** true Check the From address and Reply-to address parameters are valid for your mail relay **Text:** Check the Test Address parameter: if set, every notification is redirected to that address (common after a clone) **Critical:** true Check SSL/TLS settings and that any certificates the relay requires are in the mailer's trust store Use Send Test Message from the Notification Mailer page to prove the outbound path #### 4. Inbound processing **Items:** If email responses are used, check the IMAP server, account and password Check the Inbox, Processed and Discard folder names exist on the mail account If responses are not used, confirm inbound processing is disabled so the mailer does not fail on IMAP #### 5. Queue and notification state **Items:** Count ready messages in WF_NOTIFICATION_OUT; a growing count means the mailer is not dequeuing Check WF_NOTIFICATIONS.MAIL_STATUS for the affected notifications: MAIL (waiting), SENT, ERROR or FAILED **Text:** Check the recipient's NOTIFICATION_PREFERENCE in WF_LOCAL_ROLES: QUERY or DISABLED means no email is sent **Critical:** true Check the recipient role has a valid EMAIL_ADDRESS in WF_LOCAL_ROLES Confirm the Workflow Deferred Notification Agent Listener is running, so notifications reach the outbound queue #### 6. Background processing **Items:** Schedule Workflow Background Process (FNDWFBG) for deferred activities per item type Schedule a separate FNDWFBG run for timeouts Schedule a FNDWFBG run with stuck processes enabled, less frequently #### 7. Diagnostics **Items:** Run $FND_TOP/sql/wfmlrdbg.sql with the notification id to see its full history Run the Workflow Analyzer from My Oracle Support Doc ID 1369938.1 for an overall health report Compare mailer parameters with a working environment after any clone #### 8. Purge and housekeeping **Items:** Schedule Purge Obsolete Workflow Runtime Data for completed item types **Text:** Never purge or delete from WF_NOTIFICATION_OUT without Oracle Support guidance **Critical:** true **Text:** Disable or redirect the mailer in every cloned non-production environment before starting services **Critical:** true **Scoring Note:** Start with Service status and Logs; most mailer problems show up there. Treat any open critical item in Outbound or Queue state as the likely cause before changing anything else. ## Content **Intro:** This checklist covers the Oracle Workflow Notification Mailer on EBS 12.1 and 12.2 when emails stop, arrive late or replies are not processed. It runs from service status and log location through SMTP and IMAP settings, queue state, user preferences, background processes and safe purging. **Sections:** #### How notifications reach an inbox **Body:** When a workflow sends a notification, Oracle Workflow creates a row in WF_NOTIFICATIONS and raises a business event. The Workflow Deferred Notification Agent Listener processes it and places a message on the WF_NOTIFICATION_OUT queue. The Workflow Notification Mailer, a service component running under the Workflow Mailer Service, dequeues the message, renders it according to the recipient's notification preference and sends it through SMTP. Responses come back through IMAP into the inbox folder, and the mailer moves them to processed or discard. A break anywhere in that chain looks the same to users: no email, so check each link in order. #### Where the mailer log is **Body:** The mailer writes to a file named FNDCPGSC followed by the process id, with a .txt extension, in $APPLCSF/$APPLLOG on the node running the Workflow Mailer Service. On 12.2 that directory is under fs_ne, so it is shared between run and patch editions. To find the right file, open Administer Concurrent Managers, select Workflow Mailer Service, view the processes and note the process id. The default log level shows errors only; raise the Log Level parameter of the mailer component in Workflow Manager while you reproduce the problem, then lower it again because statement-level logging grows quickly. **Bullets:** - Table FND_SVC_COMPONENTS: COMPONENT_NAME, COMPONENT_STATUS, COMPONENT_TYPE - Queue WF_NOTIFICATION_OUT: ready messages waiting for the mailer - WF_LOCAL_ROLES: NOTIFICATION_PREFERENCE and EMAIL_ADDRESS per role #### Background processes **Body:** The Workflow Background Process (short name FNDWFBG) is a concurrent program that runs deferred activities, timed-out activities and stuck processes for an item type. It is not the mailer, but many 'notification never sent' cases are really workflows waiting on a deferred activity that no background process picks up. Schedule separate runs: deferred activities frequently (for example every few minutes for busy item types such as approvals), timeouts every hour or so, and stuck processes less often. Leaving item type blank processes all item types, which is fine for small systems but slow on large ones. #### Common mistakes **Body:** After a clone, the mailer in test either sends real emails to real users or has a Test Address that silently redirects everything; both cause confusion, so set the Test Address deliberately in every non-production environment. Users with notification preference QUERY or DISABLED never get email, which often looks like a mailer fault. Deleting messages from WF_NOTIFICATION_OUT to clear a backlog can lose notifications and corrupt the queue; only do it with Oracle Support. Finally, check that the mail relay accepts connections from the concurrent node's IP address. **Cta:** If you want admins and approvers to ask EBS which notifications are waiting and why in plain English, on your own servers, we can set up that private AI layer. **Faq:** #### Where is the Workflow Mailer log in Oracle EBS? **Answer:** In $APPLCSF/$APPLLOG on the concurrent processing node, named FNDCPGSC.txt. Find the process id for the Workflow Mailer Service in Administer Concurrent Managers. On 12.2 this directory is in the non-editioned file system, fs_ne. #### What does the Workflow Background Process do in Oracle EBS? **Answer:** Workflow Background Process (FNDWFBG) processes deferred activities, timed-out activities and stuck processes for the item type you specify. Without it scheduled, workflows wait indefinitely on deferred steps. Schedule separate runs for deferred, timeout and stuck processing at different frequencies. #### How do I troubleshoot a single notification that was not sent? **Answer:** Run $FND_TOP/sql/wfmlrdbg.sql with the notification id. It shows the notification, its MAIL_STATUS, the recipient's preference and email, and related queue messages. Check WF_LOCAL_ROLES for the recipient, then the mailer log around the send time. #### What is the Workflow Analyzer? **Answer:** An Oracle-provided diagnostic script, available from My Oracle Support Doc ID 1369938.1, that reports on workflow health: runtime data volumes, mailer configuration, background process scheduling and known issues. Run it regularly and after any mailer or upgrade change. ## Search terms oracle ebs workflow mailer log location, oracle ebs workflow mailer, workflow background process in oracle ebs, workflow troubleshoot in oracle ebs r12.2, oracle ebs workflow background process, wfmlrdbg.sql, workflow notification mailer not sending emails --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json