Human task is scheduled twice even if I set redis lock about conductor HOT 5 OPEN

@JenniferZh90 , at lease it seems the human task in your workflow working? In my workflow, the huamtask stuck , can not updated as finished. Could you share how do you update human task to finish it? Thank you!

from conductor.

@Dyson-Ido , I just first get human task id then update it with complete status:
POST "http://localhost:8080/api/tasks" with body:
{
"taskId": <task_id>,
"workflowInstanceId": <instance_id>,
"status": "COMPLETED",
"outputData" => <output_data>
}

from conductor.

@JenniferZh90 , It's actually updated as COMPLETED status? I mean the human task is completed?

from conductor.

@Dyson-Ido Yes. All tasks are marked as "COMPLETED" finally if they are completed/finished

from conductor.

@v1r3n I did replicate this issue and It seems a bug in system. With conductor client v3.9, this was occurring few times with 2-4k of load while with conductor client v3.19 (with batch poll & execute using completableFuture) Its very evident. This hangs the entire system if your next workflow trigger is waiting for this workflow to be completed.

This also doesn't mark the workflow as completed with pause and resume because one of the task instance is still in-progress.

from conductor.