🦞 igor-claw: add recipe for diagnosing a live site stuck stale after successful writes - #951
Open
ayal wants to merge 1 commit into
Open
🦞 igor-claw: add recipe for diagnosing a live site stuck stale after successful writes#951ayal wants to merge 1 commit into
ayal wants to merge 1 commit into
Conversation
…fter successful writes New troubleshooting recipe for when Editor saves, Publish Site, and even no-publish-required writes (Create Custom Embed) all report success with real revisions/timestamps, but the live-served HTML never updates. Gives agents a two-step bisection: (1) check response headers to rule out downstream/CDN caching, (2) use a Create Custom Embed probe (which docs promise applies immediately, no publish step) to isolate a publish-flow issue from a deeper origin serving/cache incident with no public-API fix — so the agent stops retrying write APIs and tells the user to escalate to Wix Support with concrete evidence instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Investigated a feedback report: a Premium customer's site had every write path — Editor saves, Publish Site, and Create Custom Embed (which the API docs say applies immediately, no publish needed) — report success with real revisions/updated timestamps, but the live-served HTML never changed. Response headers (
age:0,cache-control: private,max-age=0,must-revalidate) ruled out a downstream/CDN cache.I reproduced the write→serve path on a fresh test site and confirmed it works correctly in general (Create Custom Embed did appear live immediately, matching docs). So this specific report is a genuine site-specific serving-infra incident, not a systemic API/docs bug — no public API exists to diagnose or force-fix it. That determination itself is useful and repeatable: an agent hitting this pattern should recognize it quickly (via the same 2-step bisection I used) and stop retrying write APIs, rather than re-treading publish/republish attempts.
What this adds
A new recipe,
skills/wix-manage/references/sites/diagnosing-live-site-not-updating-after-successful-write.md, registered inSKILL.mdandyaml/wix-manage/sites/documentation.yaml:Slack thread for the originating report: https://wix.slack.com/archives/C08P5DKLJR5/p1786375972182859
This PR was opened automatically by an AI agent acting on behalf of Ayal (ayalg@wix.com) — not personally written by them.