AnsweredAssumed Answered

Are asynchronous user tasks being handled differently since the introduction of the Async executor?

Question asked by eoactiviti on Feb 15, 2018
Latest reply on Mar 15, 2018 by eoactiviti

Asynchronous user tasks are being saved in ACT_RU_JOB table and marked with the type "message".

No entry is made in the ACT_RU_TASK table and assigned Users for this User-Task are not able to complete the process.

- Is the Message Queue based Async Executor responsible for this?

If yes, why are asynchronous user tasks handled as jobs ?

In the Activiti User Guider is stated:

16.1.1. Async Executor design

Two types of jobs exist: timers (like those belonging to a boundary event on a user task) and async continuations (belonging to a service task with the activiti:async="true" attribute).


Thanks in advance.


Best regards