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

   ### 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
   
   When a workflow instance is stopped due to serial discard mechanism, its 
status changes to "STOPPED", the end time remains empty (displayed as "-"), but 
the running duration continues to accumulate indefinitely. This is clearly a 
bug.
   Additionally, I want to confirm: if this issue is not fixed, will it cause 
database field overflow and further lead to the collapse of the entire 
scheduling system?
   
   <img width="1498" height="324" alt="Image" 
src="https://github.com/user-attachments/assets/5579430c-db0b-437d-bc9c-714b46ffaec1";
 />
   
   ### What you expected to happen
   
   After a workflow instance is stopped by serial discard, its running duration 
should be set to the empty.
   
   ### How to reproduce
   
   1)Create a workflow (including Shell script and stored procedure execution) 
with a scheduled trigger (trigger every 3 minutes), and set the workflow to 
serial discard mode.
   2)Shut down all DolphinScheduler modules: worker, master, api, alert, etc.
   Wait for a period of time (e.g., 20 minutes).
   3)Restart all DolphinScheduler modules and check the workflow instances.
   4)Observe that the historical instances generated during the downtime are 
marked as "STOPPED", their end time is displayed as "-", and the running 
duration keeps increasing continuously.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.4.1
   
   ### Are you willing to submit PR?
   
   - [ ] 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