This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
We had the same issue with open ended schedules being marked as complete.
We did not work out exactly what was happening. There were a few errors in the server Event log but we could not correlate those to the failures the the last time the workflows ran, or were supposed to run.
We ended up creating replacement schedules and removing the old ones. At about the same time we also increased the RAM on the server. Although Windows was not reporting any particular memory exhaustion this did seem to provide some performance improvement and we saw less queuing of jobs which might be relevant to our case (but won't be the same in 2020.x), see below.
I was expecting to catch the cause the next time it happened but we have not had a recurrence since we set up the new schedules and increased the host server RAM.
The known issue on 2018.x is that the Scheduler seems to "lose track" once there are a certain number of jobs queued. This results in jobs being processed in LIFO order, as opposed to the FIFO order that should be happening, and thus jobs can get stuck at the front of the queue for a long time.
My understanding is that this specific issue was fixed in 2019 and subsequent versions.
The jobs that we had schedule problems with are frequently running, every 10 minutes, and so were experiencing the stuck queue issue more than others. It's not clear if that then caused the problem with the schedules but I am suspicious that they might be related since both issues went away at the same time.
@sameerpremji Please ensure you are running the latest release of Server 2021.1 (2021.1.4.26400) as there was an issue with the initial release that would cause jobs using gallery data connections to fail or get stuck which could be contributing to your issue. If you are still having issues with schedules moving to a completed state unexpectedly after updating to this version please open a support request to investigate what is happening in your environment to cause this.