How do you prevent / detect jobs that are stuck in an unexpected state?

My jobs sometimes get stuck due to unexpected behavior of the process I’m automating (e.g. a dependency is taking forever to complete).

How do you prevent this from happening? Do you have systems set up to alert you when a job is taking longer than expected to complete?

1 Like


Can you explain what are you trying to do?

I mean, if one thing is taking so much time, then you can mention the time out so that the bot will stop after that particular time. Have you tried that?


@HareeshMR mentions a good way. Check the time before the activity, and compare it to MaxTime (e.g. Now.Addminutes(15) would wait 15 minutes). If MaxTime is reached, then it’s an application error and the process can be restarted.

However, sometimes this does not work. A good example is with excel and macros. If your VBA code has any pop-up boxes or errors occur while it is running, the robot will continue running forever because it doesn’t detect an error and is stuck on that one processing step. I’ve noticed this in other proprietary applications that have pop-ups as well. As far as i know, the only way to fix that is to log in to the robot machine and click the pop-up yourself or to kill the process

1 Like