We saw an issue with VisualCron remote trigger (monitoring a remote server for Job X completion) after the remote server being rebooted/disconnected for a while. The remote trigger would not fire after job X on the remote server completes, although the trigger still looks valid. We had to manually reload the remote trigger and then cancel to make the trigger work properly. This also holds off subsequent jobs which take hours to finish and significantly delays our daily work. Is there a way to fix/avoid this issue? Thanks.

Hi,

the VisualCron Trigger is lacking the reconnection settings other Triggers have. We will implement this and notify you when it has been implemented. Thanks for the report!

---

Hi, we added reconnection alternatives for this build:

https://www.visualcron.c....aspx?g=posts&t=9532 

---