Manual runs

A manual run creates a normal check using the schedule's current saved configuration. Use it to validate a new schedule, confirm a credential rotation, investigate a failure, or test a configuration change.

Start a manual check

1. 1

   Review the schedule

   Confirm that the selected worker is online, the schedule references active source and secret metadata, and the backup pattern currently resolves to the intended file.

2. 2

   Run now

   Open the schedule and choose the manual-run action. You can also request one immediate run at the end of schedule creation.

3. 3

   Open the check

   The check normally begins as Queued, then moves through worker execution. Open it to review the selected artifact, current status, logs, probes, and notification messages.

4. 4

   Evaluate the outcome

   For a success, confirm that the expected gates—not only the restore—passed. For a failure, use its failure category and stage-specific logs to decide whether to correct the source, Secret, format, worker capacity, or validation criteria.

What a manual run changes

A manual run does not:

• move or replace the next recurring run
• activate a paused schedule for future automatic runs
• bypass worker availability
• bypass the organization's monthly check quota
• use unsaved edits

It does create a check record and can send notifications according to the schedule's saved notification mode.

See Checks for status meanings and Evidence for proof files available after eligible checks.