{"id":7419,"date":"2020-05-08T11:13:04","date_gmt":"2020-05-08T11:13:04","guid":{"rendered":"https:\/\/rax-stg-wp-aws.com\/blogs\/dba-tips-for-handling-workflow-notification-mailer-issues\/"},"modified":"2026-11-03T19:28:39","modified_gmt":"2026-11-03T19:28:39","slug":"dba-tips-for-handling-workflow-notification-mailer-issues","status":"publish","type":"blogs","link":"https:\/\/www.rackspace.com\/de\/blogs\/dba-tips-for-handling-workflow-notification-mailer-issues\/","title":{"rendered":"DBA tips for handling Workflow Notification Mailer issues"},"content":{"rendered":"

Introduction<\/strong><\/p>\n

When you manage issues, you deal with the process of recording, tracking, and resolving problems. Because Workflow Notification Mailer has many components, you might struggle to address issues related to it. To help you, I cover some issues and possible fixes. Don’t miss out on the scripts that you need to manage Workflow Notification Mailer activities easily.<\/p>\n

Workflow Notification Mailer generic issues and their fixes<\/strong><\/p>\n

The following sections explore some Workflow Notification Mailer issues and solutions.<\/p>\n

Issue: Users don’t get notifications<\/strong>
\nUsers don’t receive notification emails or cannot fix the failed notifications.<\/p>\n

Cause<\/strong><\/p>\n

The following settings are set to DISABLED<\/em> instead of MAILHTML:<\/p>\n

– PREFERENCE_VALUE<\/strong> in the FND_USER_PREFERENCES<\/strong> table
\n– NOTIFICATION_PREFERENCE<\/strong> in the WF_LOCAL_ROLES<\/strong> table<\/p>\n

FIX<\/strong><\/p>\n

1. Run the following commands to back up the tables:<\/p>\n

           SQL> create table fnd_user_preferences_bkp as select * from fnd_user_preferences;<\/em><\/p>\n

           Table created.<\/p>\n

           SQL> create table wf_local_roles_bkp as select * from wf_local_roles;<\/em><\/p>\n

           Table created.<\/p>\n

2. Run the following commands to update the tables:<\/p>\n

 select user_name,preference_value from FND_USER_PREFERENCES where preference_value = ‘DISABLED’ and preference_name = ‘MAILTYPE’ and module_name = ‘WF’ and user_name like ‘%<USER_NAME>%’; <\/em><\/p>\n

           update FND_USER_PREFERENCES set preference_value = ‘MAILHTML’ where preference_name = ‘MAILTYPE’ and preference_value = ‘DISABLED’ and module_name = ‘WF’ and user_name like ‘%<USERNAME>%’; <\/em><\/p>\n

           select * from wf_local_roles where notification_preference = ‘DISABLED’ and name like ‘%<NAME>’<\/em><\/p>\n

           update wf_local_roles set notification_preference = ‘MAILHTML’ where notification_preference = ‘DISABLED’ and name like ‘%<NAME>%’<\/em><\/p>\n

3. Run the request **Resend Failed\/Error Workflow Notifications** from the System Administrator
\n   responsibility to resend failed notifications. Set the date parameter, **Notifications sent on or after**,
\n   to the specific date.<\/em><\/p>\n

   **Note:**  Use the following format for the date: **DD-MMM-YYYY** (Example: 01-JAN-2020)<\/em>
\n <\/p>\n

Issue 2: Emails go to the wrong folder<\/strong><\/p>\n

The system delivers expense notification approval emails to the DISCARD<\/strong> folder instead of the PROCESS<\/strong> folder.<\/p>\n

The following example shows the standard approval email Action<\/strong> item generated when the approver clicks on the Approval <\/strong>link:<\/p>\n

    Action: ‘Approve’
\n    Note: ”
\n    NID[5513471\/192168752214903990869743932721878211126@WFMAIL]<\/em><\/p>\n

When the notification goes to the Junk folder,  the “Action” items appear as follows:<\/p>\n

    Action: ‘Approve’Note: ”NID5389465\/1779945055187563456464409735425450546126@WFMAIL<\/em><\/p>\n

Cause: <\/strong><\/p>\n

The Microsoft\u00ae Outlook\u00ae email creation format setting is text mode, or you approve the notifications from a mobile device.<\/p>\n

FIX:<\/strong><\/p>\n

Whenever you approve an email notification by using email text mode or from a mobile device, you should ensure that you do the following actions:<\/p>\n

– Put a space between each field.
\n– Put the NID<\/strong> value in brackets.<\/em><\/p>\n

The message from the preceding example should have at least one space between the fields, and the **NID** value should include square brackets ([ ]), as shown in the following example:<\/p>\n

    Action: Approve<\/strong>
\n    Note: ”
\n    NID[5389465\/1779945055187563456464409735425450546126@WFMAIL<\/em><\/p>\n

Issue 3: Users miss emails or get old emails<\/strong><\/p>\n

Users don’t receive emails on time, or they get old notifications that are already closed or canceled<\/p>\n

Cause:<\/strong><\/p>\n

The issue occurs when the Workflow Notification Mailer queue is full of junk data.<\/p>\n

The wf_notifications<\/em> parameter has mail_status<\/strong> set to MAIL<\/em> for closed notifications or SENT <\/em>for open notifications.<\/p>\n

In this scenario, the wf\\_notification\\_out<\/strong> queue has very old entries from the wf_notifcations <\/strong>table. This occurrence sends an anomaly notification when the Workflow Background Process request parameters are incorrect.<\/p>\n

Fix:<\/strong><\/p>\n

Use the following high-level steps to rebuild the Workflow Notification Mailer queue:<\/p>\n

1. Check with the customer about how to purge the old notifications.
\n2. Keep the date for reference, such as the begin_date<\/strong>.
\n3. Shut down Workflow Notification Mailer.
\n4. Close all the old OPEN<\/strong> notifications that are older than begin_date<\/strong>.
\n5. Update the mail\\_status<\/strong> to SENT<\/strong> for any notifications that are older than begin_date<\/strong>.
\n6. Rebuild the queue by using the following script as the APPS<\/strong> user:<\/p>\n

 SQL> @$FND_TOP\/patch\/115\/sql\/wfntfqup.sql apps <APSS_PASSWD> APPLSYS<\/em><\/p>\n

Maintenance scripts for the Workflow Notification Mailer<\/strong><\/p>\n

The commands in this section help you to maintain the Workflow Notification Mailer. You can put the commands into scripts for your convenience.<\/p>\n

Script 1<\/strong><\/p>\n

This script modifies the following settings:<\/p>\n

– RUNNING<\/em>
\n– STARTING<\/em>
\n– STOPPED_ERROR<\/em>
\n– DEACTIVATED_USER<\/em>
\n– DEACTIVATED_SYSTEM<\/em>
\n– NOT_CONFIGURED<\/em><\/p>\n

Use the following commands to update the component_status for the Workflow Notification Mailer and modify the settings:<\/p>\n

 SQL> select component_status
\n    from fnd_svc_components
\n    where component_id =
\n    (select component_id
\n    from fnd_svc_components
\n    where component_name = ‘Workflow Notification Mailer’<\/em>);<\/p>\n

  COMPONENT_STATUS
\n    ——————————
\n    STARTING<\/p>\n

\n    SQL> update fnd_svc_components set component_status=’DEACTIVATED_SYSTEM’ where component_id =
\n    (select component_id
\n    from fnd_svc_components
\n    where component_name = ‘Workflow Notification Mailer’);<\/em><\/p>\n

    1 row updated<\/em><\/p>\n

    SQL> commit;<\/em><\/p>\n

Commit complete.<\/p>\n

Script 2<\/strong><\/p>\n

You can use the following commands to set the Mailer STARTUP_MODE<\/strong> to MANUAL<\/em> or AUTOMATIC<\/em>:<\/p>\n

  SQL> select fsc.COMPONENT_NAME,fsc.STARTUP_MODE,fsc.COMPONENT_STATUS
\n    from APPS.FND_CONCURRENT_QUEUES_VL fcq, fnd_svc_components fsc where fsc.concurrent_queue_id = fcq.concurrent_queue_id(+)
\n    order by COMPONENT_STATUS , STARTUP_MODE , COMPONENT_NAME;<\/em><\/p>\n

\"dba<\/p>\n

 <\/p>\n

  SQL> update fnd_svc_components fsc set fsc.STARTUP_MODE=’MANUAL’ where fsc.COMPONENT_NAME=’Workflow Notification Mailer’;<\/em><\/p>\n

    1 row updated.<\/em><\/p>\n

    SQL> commit;<\/em><\/p>\n

    Commit complete.<\/em><\/p>\n

Script 3<\/strong><\/p>\n

This script updates the Workflow Notification Mailer password from the backend:<\/p>\n

   SQL> @wfmlrpwupd_in.sql
\n    Enter value for password: *****
\n    Enter value for componentid: 10006
\n    Updated<\/em><\/p>\n

    SQL> @wfmlrpwupd_out.sql
\n    Enter value for password: *****
\n    Enter value for componentid: 10006
\n    Updated<\/em><\/p>\n

Script 4<\/strong><\/p>\n

Use the following single script to change the Workflow Notification Mailer values from the backend:<\/p>\n

 $FND_TOP\/sql\/afsvcpup.sql<\/em><\/p>\n

\"dba<\/p>\n

 <\/p>\n

\"dba<\/p>\n

 <\/p>\n

Conclusion <\/strong><\/p>\n

The Workflow Notification Mailer has many components and some tricky issues. Make sure to back up the wf\\_\\ tables<\/strong> before updating them.<\/p>\n

Refer to the relevant Oracle MetaLink note before running a script to apply the fixes. MetaLink has many other scripts besides the ones included in this post that can help you resolve issues in the Workflow Notification Mailer.
\n <\/p>\n","protected":false},"excerpt":{"rendered":"

This post discusses a few generic Oracle® Workflow Notification Mailer issues that database administrators
\n(DBAs) face daily.<\/p>\n","protected":false},"author":2,"featured_media":7421,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","format":"standard","meta":{"content-type":"","nid":"26413","content_type":"blog","created_by":"10130","authored_on":"2023-12-22T12:13:04+00:00","field_article_industries":"","tag_category":"Technical","field_blog_author_text":"Ravishekhar Yelemane, Oracle Applications Database Administrator, Rackspace Technology","seo_description":"Discover solutions to common Workflow Notification Mailer issues, enhancing your management of Oracle Database systems.\r\n","field_featured_image":"","insights_image":"\/wp-content\/uploads\/2026\/blog_technical_images\/26413-insights_image-oracle-technical-blog-1-insights.jpg","field_partners":"","rxt_platforms":"Oracle","product":"","publisheddate":"2020-05-08T11:13:04","rxt_solutions":"Cloud Management & Operations","opengraph_tag":"","x_tag":"","teaser_flag":"Technical Blog","seo_titile":"Workflow Mailer Issues | Rackspace Technology","field_topics":"","field_slug":"dba-tips-for-handling-workflow-mailer-issues","footnotes":""},"categories":[178],"tags":[204],"class_list":["post-7419","blogs","type-blogs","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-technical"],"_links":{"self":[{"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/blogs\/7419","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/blogs"}],"about":[{"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/types\/blogs"}],"author":[{"embeddable":true,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/comments?post=7419"}],"version-history":[{"count":3,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/blogs\/7419\/revisions"}],"predecessor-version":[{"id":9447,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/blogs\/7419\/revisions\/9447"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/media\/7421"}],"wp:attachment":[{"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/media?parent=7419"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/categories?post=7419"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rackspace.com\/de\/wp-json\/wp\/v2\/tags?post=7419"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}