Calling Orchestration from E1 Page Generating an Error
We are currently running TR 9.2.8.4 and have a situation where an Orchestration when called from an E1 Composite Page in PD flags an error, but when called from the Orchestrator Studio returns as successful.
The Orchestration is designed to accept either the individual elements (MCU, OBJ, SUB) for a General Ledger code and to then create that combination in the PD, PY and DV environments. Despite reporting an error, the combination is being created in all three environments successfully.
The Orchestration submits itself to the DV and PY environments using a REST API Endpoint and authenticates using Basic Authentication and a service user profile on the Connection's Soft Coding Record. I have turned on debug for my user profile and the API connecting user and the only error that shows in the AIS logs is