Troubleshooting

Updated File But Agent Uses an Old Version?

A fast diagnosis flow for when you upload or edit a file, but the agent keeps referencing stale content.

This is one of the most common trust-break loops: you fix the document, ask again, and the answer still sounds like the old draft. Usually the file didn’t actually reach the active context (or the wrong copy is being used).

Common symptom

“I changed section 3, but it still quotes the old text.” Most cases are upload/context mismatch, not model quality.

2-Minute Recovery Checklist

Re-upload the updated file in the same chat/thread where you want work to continue.
Rename the file with a version suffix (example: proposal-v3.docx) so old and new copies are obvious.
Ask for proof: request a direct quote from a line you changed.
If proof fails, start a fresh thread and upload only the newest file.
If still wrong, share a tiny escalation packet in #help (template below).

Known-Good Verification Prompt

Paste this exactly after uploading your latest file:

Before doing any analysis:
1) confirm the exact filename you are using
2) quote one sentence that includes this marker: "[NEW-VERSION-MARKER]"
3) state whether any older similarly named files are also in context
If you cannot find that marker, stop and ask me to re-upload.

Add a unique marker like [NEW-VERSION-MARKER] to the updated file once, then remove it later. This instantly proves whether the agent can see the right copy.

Why This Happens

1) Same filename, multiple versions

If you keep reusing notes.docx, it’s easy to lose track of which version is active.

2) Different surface/context

You uploaded in dashboard chat, then asked in Discord (or another thread). Same agent identity, different conversation context.

3) Old thread inertia

Very long chats can carry stale assumptions. A fresh thread + single latest file often resolves this immediately.

4) Wrong attachment actually uploaded

Easy mistake: local folder has multiple drafts with similar names and dates.

Best practice

Use explicit versioning every time: project-brief-v1, project-brief-v2, project-brief-v3. Ask for one changed-line quote before deeper work.

High-Friction Edge Cases (Worth Checking)

1) Cloud doc vs exported file mismatch

You edited a Google Doc/Notion page, but uploaded an older exported .pdf/.docx. The agent can only use what you actually attached.

2) Same name from different folders

It’s common to have final-v3.docx in multiple folders. Confirm the local path before uploading so you don’t attach yesterday’s copy.

3) Retrying in the wrong thread after fixing the file

Users often re-upload in one place, then continue testing in another thread/surface. Keep upload + verification in the same active conversation.

4) No hard proof step before analysis

If you skip a quote/marker check, stale-context issues can hide for many messages. Always require proof first.

Stronger Verification Prompt (Metadata + Quote)

If this keeps happening, use this stricter prompt instead:

Before doing any analysis:
1) confirm exact filename you are using
2) report any visible metadata you can access (for example file type/size)
3) quote one sentence containing this marker: "[NEW-VERSION-MARKER]"
4) list any other similarly named files currently in context
If marker is missing, stop and ask me to re-upload only the newest file.

Escalation Packet (if still broken)

Surface used (Dashboard / Discord DM / server channel)
Exact filename uploaded + timestamp
Whether filename included explicit version suffix (v2/v3/etc.)
One line that changed in the new version
Agent response showing stale content
Whether fresh-thread + single-file retest was done

Don’t do this

Don’t continue for 20 messages assuming it will “eventually pick up” the new file. Verify with a changed-line quote first.