E1: ORCH: Notification Assigned to Roles Not Getting Triggered With Error 'ASYNCHRONOUS ORCHESTRATION - EXCEPTION An Exception has been caught while executing Orchestration.'
(Doc ID 3067232.1)
Last updated on JANUARY 19, 2025
Applies to:
JD Edwards EnterpriseOne Orchestrator - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
When notification is assigned based on a role and the notification process is triggered the following error is thrown .
ASYNCHRONOUS ORCHESTRATION - EXCEPTION
An Exception has been caught while executing Orchestration.
Orchestration Name : <notification>
Message : {Notification:
<notification>={Exception=Exception,
Message=No subscriptions for: NTF_XXXXXXXXXJDE in environment
JPY920. Add at least one subscription to execute the notification.}}
When checking the assigned subscriptions the notification is not present
Steps
1. Assign notification based on user role
2. Try running the notification process
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |