We are having trouble with random errors/actions that are failing and the only thing we can seem to link it to is the run mode. When we are in attended mode, there is no issue. When we are in unattended mode, it like the flow goes through a step too quickly and fails to complete actions as programmed. Sometimes, PAD doesn't recognize it failed a step and just moves forward, even though it is programmed to throw errors.
The flows are set to automatically retry upon a failure (the whole flow restarts). The first try step X will fail, then the second try, step Y, then the third, step z, etc. Essentially, we cannot pinpoint any one action being the issue and what has been a band-aid is building in retries and wait times on the specific steps that fail, but this is making our flows take too long causing backlogs.
We already standardize screen resolutions and throw errors and retries. We noticed a correlation when our organization updated to version 2.48.153.24261 in October of 2024. The flows had been working for months before this update, but now all of them are having this type of issue.
Is there any way to do a global slow down or is there a known issue/bug with unattended run mode that is causing this type of issue?
