Issue with ETL Scheduling

Some time ago, we opened a forum discussion about a problem with the ETL schedules freezing, where the scheduling would get stuck waiting for a past date. At that time, we were advised to switch to PostgreSQL, and since then we had no further issues. However, today the schedules froze again, as shown in the attached screenshot. If you need any access or further information, we are available to help investigate and identify the cause of this problem.

Version: 6.4.5.18

 

Usually if there is a problem with agent it will write a message into the log where it is located. Please post it here if there is any. 

Attached.Taking the opportunity to ask: is the "timeout for: {id}" referring to the ID of a process?

Timeout forces termination of the object execution. Say for example you have a package which takes 2 minutes to compete. You run it every 5 minutes. The package processes email messages. Now if someone sends 200 emails it will take 30 minutes to complete. But the schuduler still running and starting the package every five minutes. This might bring down the server. Another case that sometimes the package can just get stuck for example the server is not avaliable python script taking to long to complete. I hope you find my explanation useful. 
​​​
​

Understood, we will set a timeout for all schedulers with repetitive tasks, where the timeout value will always be less than the repetition interval.