Replies: 7 comments
-
Whether the X task status of the custom parameter configuration in the condition node is successful or failed, can you take a screenshot of the configuration of the condition node |
Beta Was this translation helpful? Give feedback.
-
Whether the X task status of the custom parameter configuration in the condition node is successful or failed, the result is the same. |
Beta Was this translation helpful? Give feedback.
-
some similar problems are as follows: I'll fix it later this afternoon. |
Beta Was this translation helpful? Give feedback.
-
I have the same issue here, after upgrade to version 1.3.0, all new created process have dependency issue (checked the configuration in table, No pretasks configured). anyone know to get around of this issue, even temporily? |
Beta Was this translation helpful? Give feedback.
-
you can submit another issue about 'no pretasks configured'. |
Beta Was this translation helpful? Give feedback.
-
i think we have some points about issue need to be discussed, so i will start a new discussion in mail list. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
There exists some problems in Master-Server executing logic. Some nodes could execute normally though their depenpency is not satisfied. Just like the screenshots below, if you get the same work flow, and you will find the result is wrong.
Screenshots
As you can see, task B shouldn't be executed which is the opposite of the result. When task X has condition-type node after, the tasks that depend on X will be probably executed.
Which version of Dolphin Scheduler:
-[1.3.2-snapshot]
Probable reason
Beta Was this translation helpful? Give feedback.
All reactions