Hi everyone,
I’ve noticed an issue on one of our environments where the robot machine keeps showing status “Running job”, even though there’s no active job visible in HQ.
The process itself finishes normally — no exceptions, no visible errors — but the robot doesn’t release the session. It just keeps hanging in Running state until it’s manually stopped.
Has anyone run into a similar problem or knows what could cause this?
G.
- Goran asked 2 months ago
- You must login to post comments
When you encounter a situation where the machine remains stuck in the “Running job” status even though there’s no active job in HQ, please check whether the Database Read Query Step is being used.
If it is, the connection string might look something like this:
Driver={ODBC Driver 17 for SQL Server};Server=SQLCL2INSTANCE6\INSTANCE6;Database=robotiq;UID=robotiq;PWD=password;
In that case, replace it with the following format instead:
Server=SQLCL2INSTANCE6\INSTANCE6;Database=robotiq;User Id=robotiq;Password=password;
This applies only if you’re using a SQL Server Database — just to be precise.
- Marijano answered 1 month ago
- You must login to post comments
Please login first to submit.