Thomas-HuWei commented on issue #15849: URL: https://github.com/apache/dolphinscheduler/issues/15849#issuecomment-2058165888
> > We have been using ds2. It's time to get stuck. Can you give me an approximate repair time? We don't depend on the release version. With a commit, we can cherry pick it into our fork warehouse. > > In the original design, the `force success` button can only execute at task instance in which workflow instance is finished. So the hot fix is only add a status restriction. > > I am not sure if this is suitable for you requirement. If you want to force success a running workflow instance this should be a new feature not a bug, since the runtime operation should have a new design. No. In ds2.x, if a process instance has three step, a->b->c， and all of them has 5 retry times. When b must fail, then I return the whole instance, and b still fail, and need retry at least 5 times. Now the instance is still running, then I set the b step to force success, next retry time, b will be skip, and c will run. But In ds3.2.1, this operation is invalid, I can't set b step to force success to skip and let c to run. Why not I use "run after b" to instead of force success b (means skip b), because DAG may be parallel and complex, can skip this step is the best chorice. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
