Hi,

We have 2 inconsistant problems in a number of our environments. Ranging from version 5.7.4 to 7.0.5.

The first is recognition of changes. We may delete a job for example. The following morning the job runs when it no longer exists. Even the Visual Cron start and completion messages appear. Similar problems have happened in the past when creating new triggers. The fix for us is restarting the Visual Cron service.

The second issue - We have an environment that uses write to files to trigger processes across multiple servers. This works very well, but now and again the file change is not recognised by a server, again once we restart the service it works fine.

Sorry, I have kept this quite vague as I'm not sure what kind of additional information you require.

Regards,
Gavin

The first problem sounds really strange. If you are using a newer version you should turn on "Extended debugging" in server settings. You should then have logs pointing out clearly when a Job was deleted. If it is "appearing" again we should be able to track what happened between this.

About file trigger. Same here, the extra logging will give a lot of details. What we need to know is what time you expected a new file, which file name, which job name and the log file. Please send this to support@visualcron.com.

I suggest upgrading those older servers as it is very hard to debug them.

---

Thank you. I have turned on extended debugging and will send in the log files and further details the next time this happens.