The trigger sometimes misses starting the job and intermittently skips tasks.

News Knowledge Base
, ,
1

Does the trigger occasionally fail to start the job and intermittently skip tasks?


The Orchestrator intermittently skips the job scheduled for the specified time trigger.

Resolution:

  • Validate whether the Orchestrator job is triggered by the scheduler. If the job fails, it will be reflected as " Schedule.NoJobCreated ".

Schedule.NoJobCreated failed only in below scenarios:

  1. Creation of jobs in classic folders is not permitted.
  2. Robots already have pending jobs for this process.
  3. The maximum number of jobs for this process has been reached. Review the trigger settings, robot availability, and running jobs.

  • Check if multiple jobs are running simultaneously on the same machine, causing delays in the actual process and resulting in skipped jobs.
  • The processes may overlap, causing jobs to enter a pending state, which, in turn, results in job skipping for the process.

Suggestion:

  • Adjust the timing of the processes to eliminate overlap. This will help prevent job skipping and ensure smoother execution.