[Bug] [Api] Using the TaskDefinitionController-save-single interface can lead to duplicate predecessor tasks. #16202
Comments
xiaoqisu777
added
bug
xiaoqisu777
added a commit
to xiaoqisu777/dolphinscheduler
that referenced
this issue
Jun 24, 2024
|
Please don't use the task page to create new task, there is a lot of bugs here, we don't want to change the code here, unless you want to refactor the whole process. |
|
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs. |
|
This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Search before asking
What happened
Use this API
Adding a task adds an additional front-end node,
If too many tasks are added, it can cause the workflow details to get stuck when opening.
What you expected to happen
I expect each task to have only one predecessor node,
like this
How to reproduce
use this api >1 time ,you can reproduce the problem
Anything else
No response
Version
dev
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: