Troubleshoot: Run or schedule does not start

Run now does nothing#

• Confirm at least one enabled farm is selected.
• Confirm the farm has an enabled routine containing at least one action.
• Check whether another run already owns the available concurrency slot.
• Open Environment Health and verify the background service and LDPlayer discovery are ready.
• Refresh once. Repeated clicking can queue duplicate intent in poorly understood states.

A schedule did not run at the expected time#

• The Windows PC, VRA background service and relevant user session must be available for local execution.
• The farm may have become eligible and remained queued behind other work.
• The schedule may be paused, assigned to a disabled farm or missing a routine.
• Windows timezone, daylight-saving or manual clock changes may have shifted the next run.
• A previous run may still be active or awaiting operator attention.

After a Windows restart#

1. 1

   Open the Command Centre

   Confirm the background service has started.

2. 2

   Check Environment Health

   Do not assume startup completed successfully.

3. 3

   Review the next scheduled time

   Make sure the expected cadence was preserved.

4. 4

   Run one farm manually

   Validate the environment before relying on the next fleet cycle.