When…
-device x became unavailable
And…
-timer “chromecast offline” is not running
Then…
-start timer “chromecast offline” with 300s runtime
this prevents the timer from being started before 300s have passed
Note: Chronograph has timer cards like “start and replace timer” and “start and resume timer”
This prevents for the same timer started multiple times, which could be the cause of your flow getting disabled.
(“60 triggered times and still running flows limit”: I was told to be sort of the only one with this issue according to Athom 
[Timeline] Flow disabled because it runs 60 times - #21 by Peter_Kawa)
