What status does a job have when a schedule is triggered in Orchestrator but there are no available robots to execute it?

When a job is triggered by a schedule in Orchestrator but there are no available robots to execute it, the status attributed to that job is Pending. This status indicates that the job is waiting for resources—in this case, an available robot—before it can proceed with execution.

The Pending status serves as a clear signal within Orchestrator that the job exists and is scheduled but is currently unable to run due to resource constraints. This helps users understand the flow of job management and which jobs are delayed due to the unavailability of robots.

In contrast, the In Progress status would imply that the job is actively being executed. The New status generally refers to jobs that have been created but not yet picked up, and the Failed status indicates that a job attempted to execute but encountered an error during its process. Thus, Pending is the most appropriate status reflecting the scenario of waiting for robot availability.