My Oracle Support Banner

E1: ORCH: Connector Orchestrations Are Not Displaying Errors Correctly (Doc ID 2658223.1)

Last updated on APRIL 20, 2020

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When working with an Orchestration that uses a Connector to call another Orchestration. The errors raised in the Orchestration that is called via the connector do not propagate through to the parent Orchestration. Instead the error indicates the connector has failed.

The method to get the error to appear in the calling Orchestration is to set Error Handling to "Continue", and Formatting the response with Groovy to indicate an Error. However, when doing this the HTTP Status code is set to 200, and the error is missed by the Orchestration Monitor.

In a previous version with Orchestrator 5.1, when a connector to an Orchestration would fail, the response would appear in the parent Orchestration.

The only way to have the errors appear is if Error Handling is set to Continue, but then the Orchestration Monitor does not accurately capture the true failure in the Orchestrations Components.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.