Wait for timer element

Hi Tomek,

Seems that you have a huge number of processes that use the timer element and that's why the scheduler can't process some of them in time and also I can see that the next time the timer got started is in the morning after several days. Please apply these two recommendations and there shouldn't be any problems with the timer in the future:

1) Please find the "threadCount" parameter in the root Web.config file of the application and change the value of this parameter from 5 (default) to 10 and check the result after that. We do not have a formula so to count the needed value of this parameter and if it won't help you need to try to change the value to 15 and check the timer after that.

2) The fact that the timer job was executed in the morning  can tell us that your application goes to the "idle" mode at night (Idle Timeout in IIS). 

If this is a cloud-based application please email us at support@creatio.com and ask us to disable the "idle" mode for your app and also modify the value of the "threadCount" parameter. If this is an on-site application please apply needed changes to the root web.config file and disable IIS timeout in the IIS settings.

Best regards,

Oscar