Understanding Completed Job Statuses

When a job finishes, it gets a status. This article explains what each status means: Finished, Canceled, Aborted, or Error. Knowing these statuses helps you fix problems and manage your automated tasks.

What You'll Need

Access to your Robotiq.ai account
Access to the robot's virtual machine (VM) or local machine to check logs

Understanding Job Statuses

Not every job will, or should, end with ""Finished."" The final status depends on things like how the process was set up, the quality of the input data, and how well the VM performs. Different statuses are normal. A result that isn't ""Finished"" doesn't always mean something went wrong.

Status: Finished

This status means the job ran completely and successfully. This is the best result.

Status: Canceled

This status happens when the robot can't start a job.

Common reasons include:

The robot is busy. A robot can only run one process at a time.
The machine isn't available. Check the robot's status in Settings → Robots.
A license is missing or doesn't have enough hours.

If these aren't the problem, check if the virtual machine's timezone matches your account's timezone. Also, make sure the time is set automatically on the VM.

Status: Aborted

Jobs can end with an ""Aborted"" status for a few reasons:

Manual stop from HQ: Someone stops a ""Running"" job directly from HQ using the ""Delete active job"" option.
Stop Process Step: The process itself is told to stop using a Stop Process Step. You can add a custom message that shows up in the job log.
Lost connection with the machine: If HQ loses touch with the Gatekeeper (robot machine), the job stops once the connection comes back. The message will say the system automatically canceled the job. Check the Event Viewer for machine problems.
- If only the Gatekeeper connection is lost, but the machine doesn't restart, the job keeps running. The job is marked ""Aborted"" because HQ can't tell its status without the Gatekeeper connection.
Timeout – more than 24 hours: Any job that runs for over 24 hours automatically stops.

Status: Error

This status usually points to a problem.

Process problems: Most errors come from bad setup or wrong logic within the process itself.
Machine problems: Errors can also come from the machine, even if the process is marked ""Finished."" For example, if a machine or virtual environment stops responding.
Third-party drivers: Sometimes, drivers from other companies cause problems. Check the Event Viewer or look for known issues with specific applications.

Important: If an error is about your virtual environment, Robotiq support can't help. We only fix errors within our own steps and features. We don't support how you set up processes or custom scripts (like Script Steps, Python Script Steps, batch files, VBScript).

Reviewing Job Logs

After any job that doesn't end with ""Finished,"" check the logs right on the robot's virtual machine (or local machine for a development robot) to find out what happened.

Process-related logs:
- Find logs created by the process script itself in %appdata%\Robotiq\logs.
- If an error shows up in the newest process log, it probably means there's a problem with the process.
- The ScriptExecutor log and Robotiq Handler log are also stored here.
Gatekeeper log:
- If a job fails because of connection problems with the machine, check the Gatekeeper log.
- This log is in %programdata%\Robotiq\logs.
Event Viewer:
- Check the system's Event Viewer for machine-related problems.

You can find the job ID next to the job in the Robotiq.ai platform. Use this ID to search within the Handler, Gatekeeper, and ScriptExecutor logs.

Need Help?

Can't find what you're looking for? Join the Robotiq Community to get help from other users and the Robotiq team.