Details
-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Description
Referring to user-guide: https://docs.camunda.org/manual/7.12/user-guide/process-engine/the-job-executor/:
As an end user (specially who are new), following statement about Job is not very clear.
A job is created whenever a wait state is reached during process execution that has to be triggered internally.
- In order to understand "wait state", if user reads "Wait States" section of user-guide https://docs.camunda.org/manual/7.12/user-guide/process-engine/transactions-in-processes/#wait-states, then he might get confused that wait state could also be User Task, Message and Signal. However in reality no job is created for User Task, Message and Signal. This is not explicitly mentioned in the doc.
- The meaning of "Triggered internally" may not be very clear to an end user ( specially to new users)
- The following statement does mention about the timer event or a task marked for asynchronous execution. But it could be rephrased to make it more clear that these are the only cases when Job is created.
This is the case when a timer event or a task marked for asynchronous execution (see transaction boundaries) is approached