Backup job EXPIRED — did not finish inside the window
backup job did not complete within completion windowan aws backup job failed to complete in timedid not complete within completion windowbackup job expired before completionfailed to complete in timeMatched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.
What is actually happening
AWS Backup gives every job a start window and a “Complete within” window. If the data transfer does not finish inside that time, AWS Backup stops the job and marks it EXPIRED. This is a final status, not a temporary one — the job will not resume on its own.
How to fix it
- Open the AWS Backup console → Backup plans, and select the plan whose jobs are expiring.
- Edit the backup rule → Customize backup window → increase the “Complete within” value (give large EC2/EBS resources several more hours).
- Also widen the start window so the job has time to leave CREATED and begin RUNNING.
- For very large or high-change EC2 instances, stagger schedules so fewer big jobs run at once and compete for throughput.
- Re-run an on-demand backup to confirm the wider window lets the job reach COMPLETED.
What AWS documents
AWS documents that if the transfer does not finish within “Complete within”, the job is stopped and shown as EXPIRED, and that EXPIRED is a final status.
Source: AWS Backup Developer Guide — Troubleshooting / Backup job statuses
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