Possible Causes of Orchestrator Exceptions

The following list describes the types of exceptions that can occur:

• JSON payload parse failure.

• Any non 200 status response from the HTML Server, which includes connection failures and security errors.

• Any non 200 status response from external REST calls (includes connection failures).

• Any failure to connect to an external database.

• Any failure to find orchestration components due to security errors.

• Invalid orchestration inputs, including data type conversion errors.

• Invalid form request, data request, or cross reference request due to failure to execute.

• Cross reference or whitelist not found when an orchestration is terminated.

• Any exception thrown from a Groovy script in a rule or service request.

For schedules, the following circumstances can generate an exception:

• The cron string used to invoke the schedule is invalid.

• The name of the orchestration called by the schedule is invalid.

• Failure to connect to the scheduler. For a resilient scheduler, failure to connect to the resiliency database. For more information about scheduler resilience, see "Configuring Scheduler Resilience" in the JD Edwards EnterpriseOne Application Interface Services Server Reference Guide.