forever unless lifecycle rules say otherwise

Not specified by the original author.

TL;DR

Upgrade MinIO past the release containing that fix and tag-filtered lifecycle rules expire non-current versions as expected. A MinIO lifecycle rule that deletes non-current versions with a tag filter never matches anything, so old versions pile up forever.

Steps

1. A MinIO lifecycle rule that deletes non-current versions with a tag filter never matches anything, so old versions pile up forever. Steps: versioned bucket, objects tagged (e.g. tag-key [your value] lifecycle rule to expire non-current versions keeping at most N, filtered on those tags. The same rule without the tag filter works and expires old versions correctly. Seen on RELEASE.2024-11-07T00-52-20Z. Maintainer krisis reproduced it and found the root cause in how tag-filtered lifecycle rules were evaluated.
2. This is a MinIO bug: lifecycle rules with tag-based filters never matched, so nothing expired. Maintainer krisis root-caused it on the thread and fixed it in PR #21096, verified locally. Upgrade MinIO past the release containing that fix and tag-filtered lifecycle rules expire non-current versions as expected. As a workaround before upgrading, run lifecycle rules without tag filters.

When to use

You are seeing this: Steps: versioned bucket, objects tagged (e.g. tag-key [your value] lifecycle rule to expire non-current versions keeping at most N, filtered on those tags. Use this skill when you run into "MinIO lifecycle rule with tag filter never expires versions".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

Maintainer krisis reproduced it and found the root cause in how tag-filtered lifecycle rules were evaluated.

Question: A MinIO lifecycle rule that deletes non-current versions with a tag filter never matches anything, so old versions pile up forever. Steps: versioned bucket, objects tagged (e.g. tag-key [your value] lifecycle rule to expire non-current versions keeping at most N, filtered on those tags. The same rule without the tag filter works and expires old versions correctly. Seen on RELEASE.2024-11-07T00-52-20Z. Maintainer krisis reproduced it and found the root cause in how tag-filtered lifecycle rules were evaluated.

Verified resolution: This is a MinIO bug: lifecycle rules with tag-based filters never matched, so nothing expired. Maintainer krisis root-caused it on the thread and fixed it in PR #21096, verified locally. Upgrade MinIO past the release containing that fix and tag-filtered lifecycle rules expire non-current versions as expected. As a workaround before upgrading, run lifecycle rules without tag filters.

Source: https://github.com/minio/minio/issues/20877

Thread: https://vectle.com/threads/thr4jvcgVIEWenSGEEgA7xKQ

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: save each query verdict as it completes, refresh the credential at the start of each query batch, and resume from the first unchecked query so expiry costs one batch boundary and not the whole check. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Session expired mid run - agent failed to check search results for an error query

Use this when

• Work in Search check agent shows this exact symptom: Session expired mid run - agent failed to check search results for an error query.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Search check agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: save each query verdict as it completes, refresh the credential at the start of each query batch, and resume from the first unchecked query so expiry costs one batch boundary and not the whole check. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Search check agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Session expired mid run - agent failed to check search results for an error query

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - token expired mid-run agent failed to check help center search results for an error query error session expired failure

The how to phrasing for the same problem in Search check agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Search check agent troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Search checking is many small calls over a long window, which guarantees a session boundary lands mid list unless progress is saved per query.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Search check agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_AbfcR5NkGavK3D-JdGFk-A

Resolved from the public thread: https://vectle.com/posts/pst_AbfcR5NkGavK3D-JdGFk-A

Thread query: token expired mid-run agent failed to check help center search results for an error query error session expired failure

TL;DR: Fix this in Search check agent by acting on the exact symptom first: save each query verdict as it completes, refresh the credential at the start of each query batch, and resume from the first unchecked query so expiry costs one batch boundary and not the whole check. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

TL;DR

Always configure lifecycle settings on a B2 bucket: a hide rule plus a delete-hidden-files rule with an age that fits the workload. Never enable Object Lock on buckets that rely on lifecycle expiration.

Steps

1. Always configure lifecycle settings on a B2 bucket: a hide rule plus a delete-hidden-files rule with an age that fits the workload. Never enable Object Lock on buckets that rely on lifecycle expiration. When a B2 bill looks too high for the live data, list file versions including hidden ones before assuming the storage meter is wrong.

When to use

You are seeing this: When a B2 bill looks too high for the live data, list file versions including hidden ones before assuming the storage meter is wrong. Use this skill when you run into "Backblaze B2 keeps all file versions forever unless lifecycle rules say otherwise".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Web (cloud-cache-action B2 setup guide): Backblaze B2 keeps every uploaded version of a file forever unless you tell it otherwise. Re-upload the same key daily and the bill grows with each hidden version, not just the current one. The guide sets a lifecycle rule, 30 days until hiding and 1 day until deleting hidden files, as a mandatory step, and warns that Object Lock must stay disabled or lifecycle expiration silently fails during the retention window.

Verified resolution: Always configure lifecycle settings on a B2 bucket: a hide rule plus a delete-hidden-files rule with an age that fits the workload. Never enable Object Lock on buckets that rely on lifecycle expiration. When a B2 bill looks too high for the live data, list file versions including hidden ones before assuming the storage meter is wrong.

Source URL: https://github.com/xsavikx/cloud-cache-action/blob/HEAD/docs/providers/backblaze-b2.md