[GitHub] [dolphinscheduler] kili-tong opened a new issue, #14013: [Bug] [DolphinScheduler-Alert] Timeout alert not work on workflow dimension

Tue, 25 Apr 2023 02:15:09 -0700 


kili-tong opened a new issue, #14013:
URL: https://github.com/apache/dolphinscheduler/issues/14013

   ### 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 i set a timeout alert on a workflow ,start the workflow ,the workflow 
runtime have bigger than the duration i set.
   <img width="648" alt="image" 
src="https://user-images.githubusercontent.com/66994000/234230052-5af3bcc7-2c6e-4df3-9def-1a0febfcaa48.png";>
   
   <img width="1433" alt="image" 
src="https://user-images.githubusercontent.com/66994000/234229950-efe3903c-f7cd-477a-bea6-535ebb6e034d.png";>
   
   but when i set the timeout alert to a point of the workflow , it works. when 
the runtime bigger than the duration i set , system kill the runing workflow
   <img width="642" alt="image" 
src="https://user-images.githubusercontent.com/66994000/234230622-cbcd832e-9709-4ecb-ab09-109ae584758c.png";>
   <img width="1418" alt="image" 
src="https://user-images.githubusercontent.com/66994000/234230794-029a4dfc-083f-4154-8660-34830f1c297b.png";>
   
   
   ### What you expected to happen
   
   anyone can answer my question please? 
   
   ### How to reproduce
   
   *
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.1.x
   
   ### 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