-
Notifications
You must be signed in to change notification settings - Fork 2.3k
WAIT task is not working properly (after v3.13.0) #3402
Comments
Hi @anaken will take a look and send to fix. |
Could be cl: 7c12003 caused the issue if it's from v3.13.0 but not v3.12.0? I hit issue with WAIT in DO_WHILE task, not executed according to 'duration'. // getWaitTimeout() = System.currentTimeMillis() + (timeDuration.getSeconds() * 1000), it's not offset of seconds but absolute time. If making WAIT as async task and execute() abide by the logic of 'duration' or 'until', WAIT tasks can be executed in DO_WHILE, but I'm not sure whether it's triggered more than the expected times. |
Hi @anaken! |
Add a test case for the issue Netflix#3402
WAIT Task with duration more than 30 seconds is not working verified in 3.13.5 as well. Is it working for Any one? We are using persistence as Postgres |
if you are using the conductor-postgres-persistence as persistence me too facing the same issue in 3.13.5. The sweeper will not picks the WAIT task which is already popped from queue_message table and left in infinite state until it is manually approved. |
Hi I have the same question using 3.13.5. Can you share your fix with me? thx a lot! |
Bug description
If you specify
duration
more than 30 seconds, then WAIT task will never be completed (it will be in IN_PROGRESS state).Important: This bug has appeared in v3.13.0.
Workflow To Reproduce
Expected behavior
Task should complete after duration period (go to COMPLETED state).
The text was updated successfully, but these errors were encountered: