@Ingo_Richtsmeier, I have another one question about external tasks.
I’ve switched to external tasks and use task id
as correlation id
(UUID4) for callbacks.
So I just call externalTaskService.complete()
or externalTaskService.handleFailure()
when I get success or error callback.
I suggest such approach should work even in case of parallel multi instance executions.
But I got some problem. I have a restriction from my infrastructure, that I must use unique correlation id
for each request.
So when task fails, and engine retries it, I send request to external rest-api with the same correlation id (task id).
What I could use instead of task id, that will be unique even for tasks retries?
Or maybe there is some possibility to regenerate id for failed task.
Or I could fetch tasks one by one and generate unique workerId
(UUID4) every time for each task, and when get callback find task by workerId
, but I’m not sure that it is correct behavior.