Sometimes weird behaviour is observed, and the only explanation is that something has gone completely wrong internally. What you could try is to add a new step to the workflow with the same definition, and see if the behaviour is the same. Or, I suppose it is even better if you use a sandbox to create a new workflow and define it in the same way.
It's a long shot, but no-one else has suggested anything yet - perhaps they are still sleeping?
Seing my great idea about the sandbox ( I decided to give it a shot myself. I observe the same behaviour. However, the Processing Rejected outcome is never visible in the "Outcomes" tab for the step, so that's why the workflow builder insists on deleting the branch - just as if you had removed another outcome.
If you try a different standard task you will notice that "Processing rejected" will be added to the outcomes if you check the flag.
The decision tasks are special in their behaviour - with outcomes decided by step input data, and therefore SAP must also have some special handling of them internally. I suppose they didn't foresee someone checking this flag for a decision task.
A new OSS Message seems inevitable
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.