I have a service call (A) that releases a task via the REST TaskList api. The process then subsequently calls a service task (B). My initial call (A) does not complete until service task B completes, which implies its one tx? I thought that the initiation of execution of a service task is a ‘Wait State’ (Camunda 7 tx boundary). Is this not the case, and if not, how do I force a commit?
This might be a fault in my custom client, as it occurs even when i go to a usertask. Feel free to close
So, the Camunda 8 engine is non-transactional. It’s entirely event based so everything that happens is committed as soon as it occurs… so it might be a client issue in your case.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.