Skip to main content

Resource scheduling

AvailableReviewed 24 August 2026

Resource scheduling is the CloudHealth Savings Automator job: define a stop window, estimate the saving, and run the schedule against non-production compute.

Scope to development and staging. Do not attach a stop window to production unless the owner has signed off.

Resource scheduling with weekday night and weekend stop windows
Sample weekday-night and weekend windows for non-production compute.

Before you begin​

  • Tag non-production with environment=development or environment=staging.
  • Attach those assets to a cost category so the schedule has a scope.
  • Confirm the organisation timezone.

Create a schedule​

  1. Open Optimisation → Scheduling.
  2. Select New schedule.
  3. Scope to the cost category or saved view (never the whole tenant on the first run).
  4. Set the window (for example weeknights 19:00–07:00, weekends all day).
  5. Read the estimated saving.
  6. Assign an owner.
  7. Enable the schedule.

Expected result​

In-scope instances stop at the start of the window and start at the end. Savings Tracker records the confirmed amount after the next bill.

Common issues​

IssueCheck
Instance did not stopTag, category membership, schedule enabled
Production was includedEnvironment tag and category rule
Saving is lower than estimatedInstance already stopped, or commitment covers the hours