Automation getting struck

Help Studio
,
1

Hello all,

There is an automation which has been in production for quite while, process wise there are no issues but sometimes the automation gets struck for quite some time only way to deal with that is to kill the job in orchestrator and trigger it again if done so it continues to run smoothly.

Is there anyway to fix this ?

If anyone have dealt with a similar situation your insight is much required.

Thanks,
Gautham.

2

Hello Gautham,

  1. Environment Stability: Verify the stability and reliability of the environment where the automation runs. Infrastructure issues such as network outages or server downtime can cause the automation to stall. Address any environmental issues to improve stability.

Please let me know if this works.
Happy Automation.

3

Hi @hrishikesh.k ,

All the other automations running in that VM are working fine. There is no code issues as well as there are no exceptions or faults as well.

We have tried rebooting the vm, restarting the services inside the vm too for ruling out the infrastructure related issues.

Thank you very much for your valuable input though.

Thanks,
Gautham.

4

Hi @Gautham_Pattabiraman

Slow down happens in our case when the error screenshot pile up or too many logs are generated you can do the cleaning of the system on regular basis to avoid the issue.

Also check if the application is getting stuck or actual robot. Check the utilization of the resources like RAM & CPU if they are over utilized then also your bot will get stuck.

Hope this helps :slight_smile:

5

Hi @AJ_Ask ,

We don’t have error screen shots in any automations as it is a restriction in the client environment as a way of not eating up memory.

The other points like CPU, RAM utilizations where monitored from kafka at the same time when bot is getting struck.

Also generally logs are disabled unless we face any prod issues again to save memory in the vm.

Thanks for your input.!

Thanks,
Gautham.

6

Hi @Gautham_Pattabiraman

in that RDP do you have enough ram, CPU Utilization.

Because some times if the ram memory hits 100% CPU Utilization bot will get stuck without the reason.

Better if possible can increase the ram space, in order to identify this you can open the RDP and start using different application simultaneously.

7

Hi @Baskar_Gurumoorthy ,

Thank you for the suggestion but as replied to @AJ_Ask s post we did check if the CPU and Ram utilization as well.

In fact they are not being pushed over 50% utilization also.

Thanks,
Gautham.

8

okay Gautham. are you using any sharepoint in that process, might be sometime while trying to access we may face this kind of issue its just based on my knowledge i am sharing

9

Hello,

No it is a main frame automation, The one application being used is a main frame created and used by the client.

Sure Any insight is welcome also for future ref if it is an access based issue it wouldn’t run even after killing and starting the job again.

Thank you so much for the trying to help

Thanks,
Gautham.