Skip to content- Sources: primary, discussion
- Summary: Kyle Kingsbury tested Orkes Conductor 5.3.2 through 5.5.0-rc2 and found three serious problems that made Conductor abandon or forget workflow executions or mark them completed without running their tasks, plus concurrent task execution and spurious startWorkflow errors. One cause was a sweeper that relied only on the Redis decider queue and never rechecked the Postgres records. Orkes released 5.5.6 with patches for all serious safety issues.
- Why it matters: Conductor users should upgrade to 5.5.6 and design tasks to tolerate concurrent execution, because the platform's locks cannot rule it out.