topsli opened a new issue, #16475:
URL: https://github.com/apache/dolphinscheduler/issues/16475

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   On the workflow definition page, it is not possible to set a timer for two 
processes consecutively.
   
   ### What you expected to happen
   
   On the workflow definition page, it is desired to be able to set a timer for 
two processes consecutively.
   
   ### How to reproduce
   
   1. create two processes in Workflow Definition page
   2. choose one process to set Timing, its successful
   3. choose another process to set Timing, its failed. Response message like: 
schedule 42 does not exist.
   
   Another method:
   1.Open the page of  Workflow Definition, then choose two processes,  one of 
these have set Timing and another isn't set timing
   
![timing0](https://github.com/user-attachments/assets/c5ec4bfc-9e32-4d12-bcd7-d99bf858e513)
   2. Check the Timing of a process which have set timing
   
![timing1](https://github.com/user-attachments/assets/8e98b9d9-8e4b-42e3-acb5-662e0fd9769c)
   3. Choose another process which no timing, try to set it's Timing. And then 
it response message: schedule 42 does not exist.
   
![timing2](https://github.com/user-attachments/assets/123e0472-d023-4b5d-bc50-ccee8725492b)
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.2.x
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]

Reply via email to