Futher test shows, that this behavior only exists, wenn I manualy set the external objects to inacitve, for normal runs it works.
This can be nessesary, if the external Object starts to early and not after workflowstart, so that an manuel correction is nessecary (setting ext. Objekt to inaciv). Only in this case the error occure.I don't know if this behavior was already in previous version.
Our suggestion for our customer is to start the following Object with "Go Immediately"
We need a patch for 12.2.3, because upgrading to the next minor version is very costly (need 3-4 month).
It have to be fixed in the next servicepacks 12.2.4. Therfore we don't test so much, because servicepacks only eliminates bugs, no new feature.So I'am waiting for response from Broadcom-Support.