Closed adrichem closed 2 months ago
can you share how many running workflows do you have in the system? Do you use redis or postgres as the setup?
Hi @v1r3n, Thanks for the response. There are no other running workflows. Its using redis with the config of the default docker-compose.yaml from the repo
Had the same problem with "JOIN" taking hours to finish. Changed the isAsync on the task back to "true" fixed the long delay https://github.com/conductor-oss/conductor/pull/120#issuecomment-2063583089
Hi @anzerr we are reverting this back to async https://github.com/conductor-oss/conductor/pull/194/files#diff-ebc515b9038973f4691b79e4dbbfec232800c5a87e95cc2ddbd12033b0fd2926R129
I see this is fixed on latest main.
Describe the bug Tasks with an execution time of several minutes complete successfully, but the next task is not scheduled until approx. an hour and a half later. The worker is running and idle. The task queue has a size of 0 and shows the working polling every second.
Whenever I execute the workflow below, the tasks in
fork
all run fine, The first tasks in each parallel path offork_2
complete but theno-op-worker-SET2-1-2
andno-op-worker-SET2-2-2
tasks don't execute. The execution tab in the UI shows them with status 'Not executed'Details Conductor version: Tried 3.18.0 and 3.19.0
Running based on Running Conductor Using Docker for evaluation and demo purposes.
On the Orkes playground, these type of workflows are running fine. I checked the documentation, but did not find anything that seemed relevant to configure.
Workflow definition: Here's a workflow that demonstrates the issue.
Task definition:
To Reproduce The
no-op-worker
sleeps for for requested Time and return completed state. Its instantiated like this:[WorkerTask(taskType: "no-op-worker", batchSize: 100, domain: null, pollIntervalMs: 200, workerId: "deploy-worker")]
Expected behavior I expect the next task to be scheduled for execution when its predecessor completes.