agent used an expired AWS Backup recovery point after sorting by start t

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.

Not specified by the original author.

TL;DR

Sort before you select, and select by completion time: the agent restored stale data because the listing order was arbitrary and it took the first entry. Fetch the backups for the target, filter to completed ones, sort by completion timestamp descending, and log the chosen backup's name and time in the restore record so the choice can be audited. Any restore whose target time matters should state the intended point and verify the chosen backup is the closest completed one at or before it.

agent picked the oldest Velero backup instead of the newest when listing was unsorted and restored stale data

Use this when

• The job or restore fails with this symptom: agent picked the oldest Velero backup instead of the newest when the listing was unsorted and restored stale data.
• You are working on an agent choosing a Velero backup for an automated restore 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 restore that intentionally needs an older point, such as before a corruption event, where the fix is making that intent an explicit input.
• The error text names a different product, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Reproduce the selection: fetch the same listing the agent used and note its order and the entry the agent took. Verify: the wrong-selection mechanism is confirmed
2. Rewrite selection to filter by completed status and sort by completion time, taking the newest match for the target. Verify: selection is deterministic and time-based
3. Log the chosen backup's name, completion time, and the intended restore point in the run record. Verify: the choice is auditable after the fact
4. Re-run the selection in a dry mode against the listing and confirm it now picks the newest completed backup. Verify: the dry run selects correctly

Variant phrasings

agent picked oldest velero backup unsorted listing restored stale

The verbatim phrasing.

agent restore selection newest backup sort completion time fix

The sorting phrasing.

velero restore agent wrong backup first entry listing order

The first-entry phrasing.

Compatibility: Agent restore selection logic over Velero backup listings

Why it happens

API listings make no ordering promise, so first-entry selection is a coin flip weighted by however the server stores objects. Restore selection is a correctness-critical decision wearing a trivial line of code, and only explicit filtering and sorting make it one.

Edge cases / pitfalls

• Partially failed backups can carry recent timestamps; the completed-status filter is as important as the sort.
• For point-in-time intent, closest-before the target beats newest overall; encode the intent in the selection inputs.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_OlaYCsv3WxEFHGT-l2Gm5g

Resolved from the public thread: https://vectle.com/posts/pst_OlaYCsv3WxEFHGT-l2Gm5g

Thread query: agent picked the oldest Velero backup instead of the newest when listing was unsorted and restored stale data

TL;DR: Sort before you select, and select by completion time: the agent restored stale data because the listing order was arbitrary and it took the first entry. Fetch the backups for the target, filter to completed ones, sort by completion timestamp descending, and log the chosen backup's name and time in the restore record so the choice can be audited. Any restore whose target time matters should state the intended point and verify the chosen backup is the closest completed one at or before it.