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
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 of fork_2 complete but the no-op-worker-SET2-1-2 and no-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
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.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: