Skip to content

How do I troubleshoot an AWS Backup job stuck in the EXPIRED status?

3 minute read
0

My backup job is stuck in the EXPIRED status in AWS Backup.

Short description

AWS Backup creates a job that provides details about the process when you back up your AWS resources.

The Complete within parameter defines the time that a backup's data transfer must finish. If the data transfer doesn't complete within this parameter, then AWS Backup cancels the backup and sets the status to EXPIRED.

The EXPIRED status is a final status, not a transitional status such as RUNNING. An expired backup job doesn't produce a usable recovery point. AWS Backup doesn't back up data for that window, and the resource remains unprotected until the next successful backup completes.

For more information, see Backup job statuses and Backup plan options and configuration.

Resolution

Identify the cause of the expired backup job

Complete the following steps:

  1. Open the AWS Backup console.
  2. In the navigation pane, choose Jobs.
  3. On the Backup jobs tab, enter or choose Status = Expired in the search box.
  4. Choose an expired job and review the error message and job details.
  5. Based on your error message, choose one of the following resolutions:
    If you receive "Backup Job did not complete within completion window" or "An AWS Backup job failed to complete in time," then see Increase the Complete within value.
    If you receive "Backup job failed because there was a running job for the same resource," then see Adjust backup schedules to prevent overlapping jobs.

Increase the Complete within value

To prevent backup jobs from expiring, increase the Complete within value in your backup rule.

Complete the following steps:

  1. Open the AWS Backup console.
  2. In the navigation pane, choose Backup plans.
  3. Under Backup plan name, choose your backup plan.
  4. In the Backup rules section, select the rule, and then choose Edit.
  5. Choose Customize backup window.
  6. Increase the Complete within value.
  7. Choose Save backup rule.

Note: The default Complete within value is 7 days. Increase this value if your backups are large or if overlapping backup schedules delay the start of subsequent jobs.

Adjust backup schedules to prevent overlapping jobs

AWS Backup doesn't run two backup jobs for the same resource at the same time. If a scheduled backup is ready to start but a previous job is still running on the same resource, then the new job waits for the previous job to complete before it starts.

Important: The completion window counts from the scheduled start time, not from when the job starts. If the waiting period consumes too much of the completion window, then the job fails with the EXPIRED status.

Complete the following steps to adjust your backup schedules:

  1. Open the AWS Backup console.
  2. In the navigation pane, choose Backup plans.
  3. Under Backup plan name, choose your backup plan.
  4. Review the Backup rules section for rules with overlapping start windows.
  5. Adjust the Frequency or Start within value to reduce overlap between rules that use the same resource.
  6. Choose Save backup rule.
AWS OFFICIALUpdated 2 months ago
4 Comments

Could you clarify whether expired jobs get stopped by AWS?

Your two statements above seem contradictory

  1. The EXPIRED status also indicates that there's a running job for the same resource.
  2. If the data transfer for the backup doesn't complete during the CompleteWithin time, then AWS Backup stops the backup and shows the EXPIRED status.

Also, this is what's written in the info tip popup beside "Complete within" dropdown when you edit the backup rule under "Backup window" section:

If the data transfer for backing up your resource does not complete during this period of time, AWS Backup will display the status Expired. Otherwise, the data transfer portion of your backup job completed successfully. However, for particularly large backups, the rest of the backup process might take up to several days to complete and display the status Completed.

It seems to suggest the "expired" status is informational, the job will run till completion or failure and the status will change to a final status.

replied 2 years ago

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

AWS
MODERATOR

replied 2 years ago

I want to clarify the behavior in more detail:

Let's say you have a scheduled backup "A" that is currently running, and a scheduled backup "B" is scheduled to start at 2:00 PM with a 1-hour completion window.

At2:00 PM, scheduled backup "A" is still running. What happens is that scheduled backup "B" will not start immediately — it will wait for scheduled backup "A" to complete.

When scheduled backup "A" completes — let's say at 2:05 PM — scheduled backup "B" will then start. If it completes within its scheduled window, it will succeed. If it does not complete within the scheduled window, it will fail with the status EXPIRED and the following error:

"Backup job failed because there was a running job for the same resource"

AWS

replied 3 months ago

This article was reviewed and updated on 2026-06-19.

EXPERT

replied 2 months ago