Process Job States and Their Meanings

• Running: Indicates that the bot process is currently being executed by the robot.
• Canceled: The bot process execution was manually canceled or interrupted. For example, if a new bot process with force start enabled begins while another is running, the running process job is marked Canceled.
• Success: The bot process completed execution successfully.
• Failed: The bot process execution did not complete successfully.
• Skipped: Occurs mainly in concurrency scenarios where multiple bot processes are triggered on the same robot but cannot all run simultaneously. Skipped applies when:
  • A new bot process with force start disabled is triggered while another is running.
  • Two processes are scheduled at the same time, and one has lower priority.
  • Two processes with equal priority are scheduled simultaneously; only one runs, the other is skipped randomly.
  • A bot process is triggered while the robot is waiting to log in.
  • Multiple start process requests occur before execution begins; only the first runs, others are skipped.
  • When a robot recovers from an unresponsive state, only the latest start process request within threshold runs, others are skipped.
• Abandoned: Set when a previously running process job did not update to a completed state and a new job starts. This can happen if the robot loses connectivity or encounters issues and later reconnects, marking the last known job as abandoned.

Practical Implications for ServiceNow Customers

• Monitoring these states enables customers to identify bot execution progress and handle conflicts when multiple jobs are triggered.
• The Skipped state helps manage concurrent job triggers and prioritization, preventing resource conflicts on unattended robots.
• Recognizing the Abandoned state is critical for troubleshooting robot connectivity and execution interruptions.
• Understanding when jobs are Canceled versus Skipped or Abandoned aids in effective process orchestration and error handling.