I wanted to help out if anyone was having an issue with slowness after an upgrade to 25R2. I have two instances that both have the same issue (support tickets 482453 & 482455).
Check your system monitor and look for failed Automation Scheduler exceptions. Look at the details and see what schedule is causing it. For us it’s Cross-Selling ML Generation. We disabled it manually and seems to have resolved the slowness.
What I believe is happening is in the AUSchedule DAC, the AbortCntr field is a smallint data type which is a range of -32768 and 32768. What I think is happening is it's maxed out at 32768 (failures) already and trying to add a failure to it which I think is causing a buffer overflow and it doesn’t know what to do so it’s causing the system to slow down.
We can see in AUSchedule that the AbortCntr is set to 32767.
I have manually disabled the automation schedule for it. Notice that the new “Max consecutive aborted executions” checkbox of “Do not deactivate” is checked. That would mean this schedule stays activated regardless if it fails 1 million times (overflowing AbortCntr due to the smallint data type).
If you manually deactivate it, the AbortCntr is still set which I think (haven’t looked at the code) is creating the tooltip stating it has been deactivated due to aborted executions. This is a false tooltip as it’s was disabled manually.
