🦞 igor-claw: fix bad Site Properties guidance for BUSINESS_SCHEDULE_NOT_FOUND - #853
Open
ayal wants to merge 1 commit into
Open
🦞 igor-claw: fix bad Site Properties guidance for BUSINESS_SCHEDULE_NOT_FOUND#853ayal wants to merge 1 commit into
ayal wants to merge 1 commit into
Conversation
…ESS_SCHEDULE_NOT_FOUND The recipe told agents to "set up site properties with business operating hours using the Site Properties API" as part of foundation setup, and to include "site properties" as a diagnosis step for "Business schedule not found" errors. That API is a different, unrelated resource — it never creates or fixes the Calendar business schedule that Bookings Staff Members/Calendar APIs check for, so this sent agents down a dead end. Root-caused via the Wix MCP against an owned test site: Update Business Schedule (Site Properties) returns 200 on a site with no Bookings schedule, and Create Staff Member still 404s with BUSINESS_SCHEDULE_NOT_FOUND afterwards. Also confirmed in wix-private/scheduler's SchedulesAdapter source that the two are unrelated resources, and in wix-private/velocity-infra that a persisting error despite Bookings being installed is a backend provisioning gap with no public-API fix. 🤖 Opened automatically by an AI agent on behalf of Ayal (ayalg@wix.com), researching Wix MCP user feedback. Context: https://wix.slack.com/archives/C08P5DKLJR5/p1785937398752899 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
What's broken
skills/wix-manage/references/bookings/bookings-staff-setup.mdtold agents to:"Business schedule not found"error.The Site Properties Business Schedule API (
site-properties/v4/properties/business-schedule) is an unrelated resource — it doesn't create or affect the Calendar business schedule (externalId: 4e0579a5-491e-4e70-a872-d097eed6e520) that Bookings Staff Members/Calendar APIs actually check for. Following this recipe as written sends an agent down a dead end: the Site Properties call succeeds (200), butCreate Staff Memberkeeps 404ing withBUSINESS_SCHEDULE_NOT_FOUND.This is exactly the sequence in a real feedback report: an agent hit
BUSINESS_SCHEDULE_NOT_FOUNDon Create Staff Member, called Site Properties' Update Business Schedule per docs, saw it succeed, retried, got the same 404, then also tried creating a Location — none of which touch the actual missing resource.Root cause (verified)
POST site-properties/v4/properties/business-schedulereturns200on a site with no Bookings business schedule;Create Staff Memberstill returns404 BUSINESS_SCHEDULE_NOT_FOUNDimmediately after.wix-private/scheduler'sSchedulesAdapter.getBusinessSchedule(): it looks up a CalendarSchedulebyscheduleOwnerId == VirtualBusinessResourceId, which is provisioned when Wix Bookings is installed — Site Properties never touches this.FixResourceProvisioningTask/MigrateSiteBusinessResourceToFixedIdTaskinwix-private/velocity-infra: internal-only immigrator tasks that exist specifically to repair sites where this schedule failed to provision, confirming there's no public-API self-heal path for that case.The fix
configure-default-business-hoursrecipe) instead of Site Properties, and note it's optional since Bookings auto-provisions default hours on install."Business schedule not found"troubleshooting entry into an ordered sequence: check/install Bookings first (fixes almost all cases) → explicitly do NOT use Site Properties as a fix → if Bookings is confirmed installed and it still fails, treat it as a backend provisioning gap and tell the user to contact Wix Support instead of continuing to retry workarounds.Companion docs-source PRs (same root cause, upstream reference docs):
This PR was opened automatically by an AI agent on behalf of Ayal (
ayalg@wix.com), while researching Wix MCP user feedback.Feedback thread: https://wix.slack.com/archives/C08P5DKLJR5/p1785937398752899