We're starting to get a lot of sites running into some issues with the scheduled task runner. We're up to 5 sites now impacted by this, which is becoming critical.
The thing that is happening is that the Windows scheduled task, which runs every 5 minutes, is calling TaskExecute.aspx, but that page remains running forever, which prevents the next 5 minute run from running.
This happens if one of the scheduled task jobs takes more than 5 minutes. We've been able to narrow it down to 5 minutes being the magic time. We have a mocking framework with an exactly 5 minute job and the issue occurs, if we set the job to anything less than 5 minutes, everything works correctly and the TaskExecute.aspx page finishes running and life continues happily.
We believe that this has started coming with 9.9.x, although we're not certain.
While troubleshooting today, we ran a debug build with a December 2019 version of TaskExecute.aspx.vb but the 9.12 debug version of the platform and the issue still occurs. So, it appears that the issue isn't with TaskExecute.aspx.vb (although at first I was thinking that it would be the cause).
Does anyone on the platform team know of anything at all that may have changed in the last year that introduced a 5 minute timeout somewhere. It would be preventing the aspx page from ending when the work is done if the page runs for longer than 5 minutes.