Purpose of Async Continuous in User Tasks

I see that we use “Async Continuations” in Service Tasks for creating a logical group for job executor to execute the jobs as well as for having a transactional commit of the jobs occurred earlier.

However what is the purpose of using it in User Tasks? As per my understanding, User Tasks are persistent in nature and will already have its state committed. Also it would be part of the main application thread, as it doesn’t get picked up by job executor.

So what is the benefit of selecting the “Async Continuous before/after” for a User Task.

User tasks can sometimes have listeners attached to with them, which might run before the task is committed, in some cases you might want to create a transaction boundary before the listener runs so that you can implement reties.

1 Like