🦞 igor-claw: settle Stores catalog version before product calls in setup-online-store#690
Open
ayal wants to merge 1 commit into
Open
🦞 igor-claw: settle Stores catalog version before product calls in setup-online-store#690ayal wants to merge 1 commit into
ayal wants to merge 1 commit into
Conversation
setup-online-store.md assumed Catalog V3 immediately after installing Stores. Reproduced on a fresh site: for several seconds post-install the catalog reports V1, then hits a window where V3 enforcement is already live while /stores/v3/provision/version still reports stale V1, before settling. Agents that probe with a product call and branch on 428 get alternating CATALOG_V1_SITE_CALLING_CATALOG_V3_API / CATALOG_V3_CALLING_CATALOG_V1_API errors on the same site seconds apart. Adds STEP 0: check /stores/v3/provision/version, settle it with a short bounded re-check, then commit to that version for the whole recipe instead of reactively flipping endpoint families on 428. Opened automatically by an AI agent on behalf of Ayal (ayalg@wix.com). Slack thread: https://wix.slack.com/archives/C0BDXM5LLE7/p1784735372076189
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.
Summary
setup-online-store.mdassumed Catalog V3 immediately after installing Stores. Reproduced on a freshly-provisioned managed-headless site: for several seconds post-installGET /stores/v3/provision/versionreportsV1_CATALOG, then there's a ~1-2s window where product enforcement has already switched to V3 while the version-check endpoint itself still reports the staleV1_CATALOGvalue, before both agree (fully stable ~8s after install in testing).428(as this recipe implicitly encouraged by assuming V3) gets alternating428 CATALOG_V1_SITE_CALLING_CATALOG_V3_API/428 CATALOG_V3_CALLING_CATALOG_V1_APIon the same site seconds apart — exactly the friction reported by a user building a Wix Headless pet-supply store./stores/v3/provision/version, settle it with a short bounded re-check (since the check endpoint itself can lag), then commit to that version for the whole recipe — no reactive endpoint-family flipping on 428. Also cross-references this fromSETUP.md's stores install step.wix-manage's sibling recipe (setup-online-store-catalog-v3.md) already checks the version once via this same endpoint; this bringswix-headlessto parity and hardens the check against the observed settle window.This PR was opened automatically by an AI agent on behalf of Ayal (
ayalg@wix.com), researching headless-platform feedback.Slack thread: https://wix.slack.com/archives/C0BDXM5LLE7/p1784735372076189
Test plan
provision/version+ V1/V3 product query every ~1.3s) — confirmed the V1→transitional→V3 sequence described above.GET /stores/v3/provision/versionis a valid, working endpoint on a live site.