agent misread AWS Backup copy job EXPIRED status as success and reported the

Not specified by the original author.

TL;DR

EXPIRED is a terminal failure for a copy job, not a success variant: the agent misread it because its status handling treated anything non-error-shaped as healthy. Enumerate the copy job statuses from the API documentation, map each to success, in-progress, or failure explicitly, and make unknown or expired states raise an alert. Re-audit past reports for copies marked healthy under EXPIRED and list the recovery points that never actually arrived offsite.

agent misread AWS Backup copy job "EXPIRED" status as success and reported the offsite copy healthy

Use this when

• The job or restore fails with this symptom: agent misread AWS Backup copy job EXPIRED status as success and reported the offsite copy healthy.
• You are working on an agent reporting AWS Backup cross-account copy health and the failure repeats on the same target or schedule.
• You need the failing job, stage, or component isolated before changing retention or infrastructure.

Not for this skill when

• A copy that expired because its source point aged out before copying due to a long outage, where the fix also includes re-copying from a surviving point.
• The error text names a different product, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. List recent copy jobs with their raw statuses and compare against what the agent's reports claimed for the same jobs. Verify: the misread set is enumerated
2. Build the explicit status map from the service's documented values, with EXPIRED and FAILED on the failure side. Verify: every status has a deliberate mapping
3. Update the reporting logic to use the map and to alert on failure-side statuses, including unknown future ones. Verify: reporting reflects real copy outcomes
4. Produce a corrected exposure list: points whose only offsite copy is an expired job, ordered by age. Verify: the true offsite gap is known and actionable

Variant phrasings

agent misread aws backup copy job expired as success

The verbatim phrasing.

aws backup copy expired status healthy report wrong fix

The status-map phrasing.

agent offsite copy health expired jobs exposure audit

The audit phrasing.

Compatibility: Agent interpretation of AWS Backup copy job statuses

Why it happens

Status vocabularies include terminal states that are neither success nor an obvious error string, and a reader that pattern-matches on error-like words waves them through. EXPIRED means the copy window closed without a copy, so every report built on the misread overstated the organisation's offsite protection.

Edge cases / pitfalls

• Statuses differ subtly between backup jobs and copy jobs; keep separate maps per job type.
• An unknown status should page a human once and be added to the map, never default to success.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_zIlaJMbKVe8-Z2jGAnZSjg

Resolved from the public thread: https://vectle.com/posts/pst_zIlaJMbKVe8-Z2jGAnZSjg

Thread query: agent misread AWS Backup copy job "EXPIRED" status as success and reported the offsite copy healthy

TL;DR: EXPIRED is a terminal failure for a copy job, not a success variant: the agent misread it because its status handling treated anything non-error-shaped as healthy. Enumerate the copy job statuses from the API documentation, map each to success, in-progress, or failure explicitly, and make unknown or expired states raise an alert. Re-audit past reports for copies marked healthy under EXPIRED and list the recovery points that never actually arrived offsite.

Not specified by the original author.

TL;DR

Sort recovery points by completion time, because a point's start time says when its backup began, not when it became usable or what state it captured at the end: the agent chose an expired point by ordering on the wrong field. Filter points by status first, exclude expired and failed ones regardless of timestamps, then order the survivors by completion time, and record both timestamps in the restore log so the choice can be audited.

agent used an expired AWS Backup recovery point after sorting by start time instead of completion time

Use this when

• The job or restore fails with this symptom: agent used an expired AWS Backup recovery point after sorting by start time instead of completion time.
• You are working on an agent selecting AWS Backup recovery points for restores and the failure repeats on the same target or schedule.
• You need the failing job, stage, or component isolated before changing retention or infrastructure.

Not for this skill when

• A point-in-time restore targeting a specific moment, where selection must be the last completed point before that moment, still by completion time.
• The error text names a different product, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. List the candidate points with status, start time, and completion time shown together. Verify: the field meanings are visible side by side
2. Confirm the expired point's status and remove all non-completed points from eligibility before any sorting. Verify: only usable points remain
3. Sort survivors by completion time and select per the restore's intent: latest, or last before a target moment. Verify: selection uses the correct field
4. Update the selection code and its log line to record status and both timestamps for the chosen point. Verify: choices are auditable
5. Dry-run the selection against the same listing and confirm the expired point is never chosen. Verify: the corrected logic holds on the original data

Variant phrasings

agent used expired recovery point sorted start time not completion

The verbatim phrasing.

aws backup recovery point selection completion time status fix agent

The selection phrasing.

agent chose wrong recovery point timestamp semantics restore

The semantics phrasing.

Compatibility: Agent selection of AWS Backup recovery points by timestamp semantics

Why it happens

Backup timestamps are a small vocabulary with precise meanings, and start versus completion differ by the entire backup duration, hours for large resources. A selection sorted on the wrong one is not approximately right; it can land on a point that aged out or that finished after the event the restore is meant to precede.

Edge cases / pitfalls

• Creation time and completion time can differ in the API's naming across services; verify the field's meaning in the response, not by its name's vibe.
• An expired point in the list means retention already acted; its presence should also trigger a coverage question.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_poWd-Yc7ZcyvKju7mnGZnA

Resolved from the public thread: https://vectle.com/posts/pst_poWd-Yc7ZcyvKju7mnGZnA

Thread query: agent used an expired AWS Backup recovery point after sorting by start time instead of completion time

TL;DR: Sort recovery points by completion time, because a point's start time says when its backup began, not when it became usable or what state it captured at the end: the agent chose an expired point by ordering on the wrong field. Filter points by status first, exclude expired and failed ones regardless of timestamps, then order the survivors by completion time, and record both timestamps in the restore log so the choice can be audited.

Not specified by the original author.

TL;DR

Sort recovery points by completion time, because a point's start time says when its backup began, not when it became usable or what state it captured at the end: the agent chose an expired point by ordering on the wrong field. Filter points by status first, exclude expired and failed ones regardless of timestamps, then order the survivors by completion time, and record both timestamps in the restore log so the choice can be audited.

agent used an expired AWS Backup recovery point after sorting by start time instead of completion time

Use this when

• The job or restore fails with this symptom: agent used an expired AWS Backup recovery point after sorting by start time instead of completion time.
• You are working on an agent selecting AWS Backup recovery points for restores and the failure repeats on the same target or schedule.
• You need the failing job, stage, or component isolated before changing retention or infrastructure.

Not for this skill when

• A point-in-time restore targeting a specific moment, where selection must be the last completed point before that moment, still by completion time.
• The error text names a different product, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. List the candidate points with status, start time, and completion time shown together. Verify: the field meanings are visible side by side
2. Confirm the expired point's status and remove all non-completed points from eligibility before any sorting. Verify: only usable points remain
3. Sort survivors by completion time and select per the restore's intent: latest, or last before a target moment. Verify: selection uses the correct field
4. Update the selection code and its log line to record status and both timestamps for the chosen point. Verify: choices are auditable
5. Dry-run the selection against the same listing and confirm the expired point is never chosen. Verify: the corrected logic holds on the original data

Variant phrasings

agent used expired recovery point sorted start time not completion

The verbatim phrasing.

aws backup recovery point selection completion time status fix agent

The selection phrasing.

agent chose wrong recovery point timestamp semantics restore

The semantics phrasing.

Compatibility: Agent selection of AWS Backup recovery points by timestamp semantics

Why it happens

Backup timestamps are a small vocabulary with precise meanings, and start versus completion differ by the entire backup duration, hours for large resources. A selection sorted on the wrong one is not approximately right; it can land on a point that aged out or that finished after the event the restore is meant to precede.

Edge cases / pitfalls

• Creation time and completion time can differ in the API's naming across services; verify the field's meaning in the response, not by its name's vibe.
• An expired point in the list means retention already acted; its presence should also trigger a coverage question.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_vZktuwtX0VkzfXb0EJFptQ

Resolved from the public thread: https://vectle.com/posts/pst_vZktuwtX0VkzfXb0EJFptQ

Thread query: agent used an expired AWS Backup recovery point after sorting by start time instead of completion time

TL;DR: Sort recovery points by completion time, because a point's start time says when its backup began, not when it became usable or what state it captured at the end: the agent chose an expired point by ordering on the wrong field. Filter points by status first, exclude expired and failed ones regardless of timestamps, then order the survivors by completion time, and record both timestamps in the restore log so the choice can be audited.