I'm seeing a Confirm BOD containing the error ServiceContainerException: No destinations available for scripting, even though my Data Flow successfully delivers a custom BOD to LN and the transaction completes successfully.
The Data Flow receives a Process.ItemMaster BOD from EQ. It checks for the presence of a project number and, if one exists, executes a Script activity that wraps the original Process.ItemMaster inside a custom Process.PcsProject BOD. The custom BOD is then sent to our on-prem LN environment.
The Data Flow behaves exactly as expected:
- The Script validates successfully in the Script editor.
- The generated
Process.PcsProject BOD is correct in OneView. - LN receives and accepts the BOD.
- The business transaction completes successfully.
However, every successful execution also generates a Confirm BOD containing:
ServiceContainerException:
No destinations available for scripting
Although processing succeeds, these Confirm BODs create unnecessary noise in our environment. I'm trying to determine why ION believes there are "no destinations available for scripting" when the custom BOD is clearly reaching LN.
Has anyone encountered this behavior before, or can you suggest what configuration or routing issue might cause this Confirm BOD to be generated?
(Full stack trace included below if it helps.)
The screenshot below shows the complete Data Flow. Only the 1 branch executes the Script activity. The Script outputs directly to the LN_PROJECT connection, while the 2 branch sends the original ItemMaster BOD to LN_NO_PROJECT. Both branches complete successfully, but only the Script branch generates the Confirm BOD containing the exception.
Has anyone seen this exception when using a Script activity to generate a custom BOD? I'm wondering if this indicates a configuration issue, an undocumented requirement for Script activities, or a defect in ION itself.
ION version: 2026.06.02.11.896ae2d Cloud Edition
