So I have this automation where it routes an email.
This automation works finely everyday without it being stuck in a running state.
But suddenly now I found that it was stuck on running state since yesterday.
Does this happen to be a bug?
Is there a way to trace what happened? Because the logs, trace and job details don’t show anything important.
Thank you in advance!
Do you have live streaming enabled of ao please check if there is any specific pop up or so
What activitirs are you using for email? Is it o365 or outlook?
If outlook it might be possible that the user might be logged out and if login screen comes it would get stuck
If above is not the issue check the event viewer logs with the timestamp from last log in orchestrator and see if there are any errors reported there..that might point in a direction
Cheers
Thank you very much.
Hi @Nahte_16
It may not necessarily be a bug. Sometimes a job stays in Running if it is waiting for an email response, application, network, or some activity to complete.
I would first check the last activity executed and add logs before/after the important steps. Also check the Robot/Orchestrator connection and machine resources.
This should help identify where exactly the process got stuck.