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
{{ message }}
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
Describe the bug
Hi -- I'm experiencing a situation that occasionally workflows will have all of their tasks complete, but the workflow itself doesn't end up complete. I was only able to replicate the issue on a conductor server that had a concurrency > 1. When it was just a single pod, the issue did not appear to happen.
If you look at the logs at the bottom of the issue, the 4th from bottom sets the workflow to COMPLETED. Then the 2nd from bottom changes it back to RUNNING.
Describe the bug
Hi -- I'm experiencing a situation that occasionally workflows will have all of their tasks complete, but the workflow itself doesn't end up complete. I was only able to replicate the issue on a conductor server that had a concurrency > 1. When it was just a single pod, the issue did not appear to happen.
If you look at the logs at the bottom of the issue, the 4th from bottom sets the workflow to COMPLETED. Then the 2nd from bottom changes it back to RUNNING.
Details
Conductor version: 3.11.0
Persistence implementation: Postgres
Queue implementation: Postgres
Lock: Redis
Workflow definition: parent workflow & child workflow
Task definition: https://gist.github.com/sawmonaco/84762ba10b7fbf6518b894415c41d055
Event handler definition:
Worker: https://gist.github.com/sawmonaco/72b2f0161a5f0559cc4692b10bc4d0cb#file-conductor_worker-py
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect all to finish
Screenshots
Additional context
Relevant logs:
The text was updated successfully, but these errors were encountered: