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"
Original Message:
Sent: 09-18-2019 10:16 AM
From: Hans-Juergen Zintl
Subject: MessageU00011516 Cannot find status definition: 'ENDED_INACTIVE'
I have an issue about external dependencies in an Workflow.
Inside the workflow are two external Jobs which have to start after workflowstart.
I start the workflow, set both external jobs to ENDED_INACTIVE and get following error in the Job after the external jobs: