DOCUMENT OPS

Audit R2 for orphaned asset versions no longer referenced in the Coda manifest

Weekly, an agent cross-checks R2 objects against the live Coda manifest, flags versions no longer referenced by any active release.

CategoryDocument Ops
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionList R2 objects in asset bucketCloudflareCloudflare R2
  • ActionRead referenced versions from Coda manifestCodaCoda
  • LogicIdentify orphaned keys outside safety window
  • OutputFile cleanup review issue in LinearLinearLinear

What it does

Keeps the CDN bucket from accumulating dead weight. An agent compares every object in the R2 asset bucket against the versions still referenced by active releases in the Coda manifest, identifies orphaned keys, and opens a cleanup review so nothing is deleted blindly.

When to use it

Use it when fast-moving Figma exports have piled up many superseded versions in R2 and you want storage hygiene with a human checkpoint before any deletion — not an automatic purge.

How it works

  1. 1A weekly schedule starts the audit.
  2. 2The agent lists all R2 objects in the asset bucket and reads the manifest of referenced versions from Coda.
  3. 3It reasons over the two sets to find keys not referenced by any active or pinned release, ignoring recent uploads inside a safety window.
  4. 4It summarizes the orphan candidates with sizes and last-modified dates.
  5. 5It files a Linear issue listing the candidate keys and reclaimable storage for an engineer to approve before deletion.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Cloudflare R2Object storage, S3-compatible.
  2. 2
    Connect CodaDocs, packs, automations.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.