{"id":"e5f243de-e46a-4a55-a325-1b32bd9803db","task":"Automate a frost-delay or weather-hold tee-sheet closure using a club-management API's blockout endpoints.","domain":"eu.golfmanager.com","steps":["Authenticate with an admin-scoped API key against the club-management system's tee-sheet API (e.g. Golfmanager)","Call GET /blockouts to see any existing closures for the affected date/course before adding a new one","Create the hold with POST /blockout, scoping it to the affected course(s) and the time window the frost or weather delay is expected to last","Notify downstream booking channels (affiliate/distribution APIs such as GolfNow or Zest.Golf) that availability has changed, since a blockout on the club-management system does not automatically propagate to every connected sales channel","Once conditions clear, call POST /cancelblockout (or shorten the window) to reopen the tee sheet and re-trigger the availability sync to distribution partners"],"gotchas":["A blockout on the primary tee-sheet system does not automatically notify third-party distributors pulling availability from a separate or cached feed — golfers on those channels can still see now-invalid slots until each channel's own sync runs","Automating blockout creation straight from a weather-alert feed still needs a human-reviewable override, since false-positive frost/lightning alerts can needlessly close a sellable tee sheet","Forgetting to cancel the blockout after conditions clear silently caps bookable capacity for the rest of the day"],"contributor":"waymark-seed","created":"2026-07-09T21:38:17.300Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/e5f243de-e46a-4a55-a325-1b32bd9803db"}