Scheduler runs repeatable CanaryWP workflows on a recurring cadence.
When to use Scheduler
Use scheduling for work that should happen consistently, such as:
- Site checks
- Maintenance verification
- Backups
- Supported update workflows
- Scripts
- Reports
Create a job
A scheduler job generally requires:
- Name or identity
- Target instance
- Cadence
- Selected action
- Action-specific configuration
- Enabled state
Cadence
Supported jobs can use intervals such as:
- Hourly
- Daily
- Weekly
- Monthly
Use the least frequent cadence that still meets the operational need.
Target
Always verify the target instance.
A scheduled task continues to run without someone manually selecting the environment every time, so an incorrect target can create repeated unwanted actions.
Job actions
Depending on availability, jobs can include:
- Maintenance/update actions
- Backup
- Script execution
- Site Testing
- Email/report output
Enable and disable
Disable a job when you temporarily want to stop future executions while retaining the job and its history.
Delete only when the job is no longer required.
Run history
Review run history for:
- Status
- Start time
- Duration
- Target
- Output
- Failure information
Failed scheduler runs
Do not assume the next run will automatically fix the previous failure.
Investigate repeated failures.
Check:
- Instance state
- Credentials
- Target
- Action configuration
- Runtime health
- Error output
Automation best practices
Start automation in testing environments.
Keep jobs narrow.
Review history regularly.
Do not automate a risky maintenance process until the manual version of the workflow is understood and repeatable.