Notification Bridge in Windows Client API Posted June 18, 2019 This is awesome. This is likely to be an interim plan for me while I write something more custom tailored for me. I would suggest you return a unique value for maintenance mode, rather than the same as a failure to run. The reason for this is many people will need to error on a failed polling the same as if the script returned bad stuff, but we would not want to do the same if its in maintenance mode. Looking at the code it doesn't look to hard to change since you already checking separately, but if i'm understanding the code correctly you would only need to return something other than false, and then change your if/else logic and maybe internal documentation. (And then we could use pulseway alerting for say a scheduled task more easily to alert on a poll failure) One question, is there a way (this could be more pulseway app 101) to make it so that if we failed to receive data within a period of time, that an alert will be sent? (say the machine is removed from the network and the pulseway client is not operable) Another question, when sent alerts this way, what do we really have for historical record keeping?