Async continuation before gateway

[tiesebarrell]

I have part of a process that looks like this:

ServiceTask1 -> ExclusiveGateway -> Other tasks

The issue I'm facing is that the invocation in ServiceTask1 is not idempotent. So once it's been done once, it should not be done again. If there were a single activity immediately after ServiceTask1 I could make it async to solve this. Since it's a gateway instead, I would have to mark all of the potential following activities as async to be sure.

Alternatively, I could add a dummy activity after ServiceTask1 just so I can set the async attribute, but that adds unnecessary clutter to the process diagram.

Is there another, more convenient way to do this I'm not seeing?

[trademak]

You describe the alternatives quite well. I don't see any other alternatives as well.
Making gateways asynchronous isn't easy, because joining parallel gateways should not be asynchronous for example.

Best regards,

[tiesebarrell]

OK, thanks Tijs. I guess there are no other options then. I think I'll stick with an extra ServiceTask.