You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Whenever the task fails, workflow status has to be updated as failed. When the workflowExecutionLockEnabled is set to true, this particular flow tries to acquire the new lock over existing lock without releasing it. Thus, the workflow state transition to failed status takes lockLeaseTime time (default 60 seconds) which is not the intended.
Describe the bug
Whenever the task fails, workflow status has to be updated as failed. When the
workflowExecutionLockEnabled
is set to true, this particular flow tries to acquire the new lock over existing lock without releasing it. Thus, the workflow state transition to failed status takeslockLeaseTime
time (default 60 seconds) which is not the intended.Details
Conductor version: v3.19.0
Persistence implementation: Postgres
Queue implementation: Postgres
Lock: Postgres
Workflow definition:
To Reproduce
Steps to reproduce the behavior:
conductor.app.workflowExecutionLockEnabled
astrue
Expected behavior
Workflow should get failed immediately after task failure as per the workflow execution flow handled in code.
The text was updated successfully, but these errors were encountered: