We have been experiencing an error where a nightly process which normally runs in about 2.5 hours, ends up just sitting there for a few hours before trying to start, then times out after 5 hours. The description from the person I’m posting this for is this:
"We process all active projects nightly, and have for many years without any issues. Normally it processes about 1550 active projects in 2.5 hours (for MITUS only). Via SC we ran MITUK at 9:00 (takes 9-10 minutes) and MITUS at 9:30pm. Via FA we run MITUK at 9:00 and MITUS runs once completed, i.e. around 9:10pm.
Since 12/28/24, we’ve had long running (4 - 6 hours) that complete, and several that run around 5 hours and then error. We’ve rebooted just the app server, we’ve rebooted all servers, we’ve rebooted both app and db servers. Each attempt has resulted in limited; meaning maybe we get it to run again, but in a day or more it fails or runs long; but we have not had continued success."
SC=Service Connect, FA=Function App, MITUS and MITUK are two of the companies we have setup.
We have been running this with Service Connect for years without major issues, once in a while we’d hit that error but we’d just re-run it and it would complete. We have a developer working with Azure Function Apps to replace Service Connect, but it doesn’t seem (to us at least) that the process should be different, all we are doing is collecting a list of Projects and sending it to the Task Agent to run Build Project Analysis.
Any ideas would be appreciated!