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" is a real answer.
1
In plain terms. Should I fix one stuck booking now, or wait for a person to do it? A resident's apartment tour for tomorrow got confirmed on our side, but we never told the property's AppFolio account about it, because of a gap I just found (and already fixed for future bookings). I have one safe, reversible command ready that corrects just this one booking and sends it over. What do you want to do?
The full question, as raised
Western Slope, property appfolio-163, inquiry fb52dbe0-993d-... / tour 17fb8e99-..., intent gc:schedule_showing:fb52dbe0-26e7-4a45-b50e-4ba7458a8454:17fb8e99-4bdb-4d56-b8ee-7e6826456f3a parked 'failed'. Root-cause fix in PR #17280 (propflowai). This one row predates the fix and needs a manual correction+redrive: scripts/guest-card-intent-redrive.ts <intentKey> --correct-unit appfolio-163-249 --reason 'org-home listing resolved via OrgListing.unitId (card 2989, PR #17280)' --apply (dry run first, no --apply).
Why, and what was tried
The session raising this recommends: Run the one-time fix now It only touches this one already-broken booking, mirrors a recovery tool already used for the same situation before, and the tour is tomorrow. Tried first, unsuccessfully: Traced the production rows behind the alert, found the root cause (scattered-site homes have no AppFolio unit mapping path), shipped a tested code fix (PR #17280) so this stops happening — but the fix doesn't repair rows already stuck, so this one booking still needs a one-time manual correction.