I want to do retrying on a service task, but use a fallback path whenever the retries do not lead to a successful result. A naive modeling would be e.g. this:
I could write an incident handler to be called at the right moment, when all retries are done. But I cannot send a message like the modeles one - as the engine has not yet entered the node (because auf asyncBefore=true).
Any spontaneous ideas how to implement such a behavior?
Another route I could envision is to code an own behavior and then check for the retry count of the job. If 0 a BPMN-error is raised instead of just throwing an exception from the attached delegate. What do you think? Then it would look like this: