I'm parked on you

Pick an option on each card and press Done; your answer goes straight back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.

1

In plain terms. What should Smith do about a tour-booking slot that is stuck? A booking attempt tried to reserve a 30-minute tour slot for tomorrow at 10am Denver time, on the building Smith uses to test the phone booking system. The reservation got marked as in-progress but never finished — there is no tour on record for it anywhere, and the error logs show nothing wrong at that moment. The slot has been stuck for about a day now, blocking that exact time from being booked again. Smith checked every place a finished booking would show up and found nothing, so it looks safe to assume no real tour or calendar invite ever happened.
The full question, as raised

stuck-tour-slot-sweep flagged reservation 663ef4c3-a188-4503-a017-3dccaa1234ea on mailbox propflow.ai@outlook.com, holderPropertyId appfolio-45 (the Test Property), interval 2026-10-14T16:00-16:30Z, submittedAt 2026-10-13T19:35:52Z, state=submitted, tourId absent, providerEventId absent. Queried PROP#appfolio-45/TOUR# partition (219 rows) — none carry this reservationId in slotReservation. Sentry query for firstSeen:-2d around applyTourIntent / tour-slot-hold returns zero issues. Code trace: writeFirstInvite() and retryTourCalendarWrite() are the only two call sites that create a calendar event, and both require an already-saved Tour row and both call bookTourSlot(claim, tour.id, eventId) immediately on a successful write, which flips state to booked. Since no Tour row anywhere references this reservationId, no code path could have reached the calendar write for it — the crash happened between submitSlot (held->submitted) and saveTour. Safe recovery is releaseSlot/releaseTourSlot on this one row, which is a DynamoDB Delete against propflow-prod — a hard-stop action for an autonomous decider run without a human decision, however confident the analysis.

Why, and what was tried
The session raising this recommends: Free up the slot now
No tour or calendar invite was ever created for it, so nothing is protected by waiting.
Tried first, unsuccessfully: Looked up the exact stuck reservation in the database, checked all 219 tour records on that building for any reference to it (none found), checked the error-tracking system around the time it got stuck (nothing recorded), and traced the booking code to confirm a calendar invite is only ever marked as sent right after a tour record is saved — which never happened here.

21c384ee is parked on this.

Pick an option above, then press Done.
PropFlow Docs