Define better terms for WAITING and DELAYED states
Bug #1470369 reported by
Dmitri Zimine
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
High
|
Renat Akhmerov | ||
Liberty |
Fix Released
|
High
|
Renat Akhmerov |
Bug Description
Changed in mistral: | |
assignee: | nobody → Renat Akhmerov (rakhmerov) |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in mistral: | |
milestone: | 1.0.0 → none |
To post a comment you must log in.
So just to have all explanations at one place I'll summarize the semantical difference.
WAITING - workflow execution cursor already reached the task but it won't run until required triggering conditions are met. For "join" task the condition is completion of its inbound tasks. So the task may be hanging in this state forever.
DELAYED - This is basically a flavor of RUNNING state which means that task will eventually complete (with success or error), all triggering conditions are met. But the task is postponed for some period of time. Currently, this state is only needed for policies.