Home / AWS Backup errors

Job stuck in CREATED then EXPIRED — start window too short

Warning CREATED AWS Backup
What AWS reports
window time has run outdid not start

Matched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.

What is actually happening

During the start window a job stays in CREATED until it begins. AWS Backup keeps retrying to begin a retryable job about every 10 minutes until it starts (RUNNING) or the start window runs out (EXPIRED). A short start window plus a busy schedule means jobs expire before they ever start.

How to fix it

  1. Increase the start window in the backup rule so queued jobs have time to begin.
  2. Spread schedules across the night instead of firing every plan at the same minute.
  3. Confirm the backup vault and IAM role are healthy so retries can succeed.

What AWS documents

AWS notes a job stays in CREATED and is retried roughly every 10 minutes until it starts or the start window ends.

Source: AWS Backup — StartBackupJob API reference

Stop finding this one failure at a time

BackupLens watches every AWS Backup job across every region, matches each failure against this catalogue automatically, and sends you the cause and the fix — instead of a job list you have to read line by line at 3am.

Start free trial