Support topics

Account, Gmail, and data controls

On your dashboard you can turn off forwarding, clear the saved Gmail app password, and disconnect Gmail send OAuth. You can also revoke Chula Sync in Google Account permissions. To delete your Chula Sync account and tenant data, email [email protected] from your account email. We will verify the request before deletion.

Set up the dedicated Hosting inbox

Enable Google 2-Step Verification, create an app password named Chula Sync, then save the dedicated Hosting Gmail address and app password on your dashboard. Public inbox OAuth is not used. Your Google Workspace administrator may need to permit app passwords.

Double-book alert

Possible resort booking overlapping an Airbnb stay (Self Marketed nights are excluded). Check Chula calendar and Airbnb; resolve the conflict manually.

Stale import

Near-term Chula blocks missing from Airbnb export after the stale-hours threshold. Confirm Airbnb IMPORT URL, wait for lag (hours), re-check export. Long 1BR default-closed ranges may intentionally not alert.

Forward failure

Gmail→Chula MIME did not send. Common causes: missing RFC822, Hosting inbox auth (app password), send OAuth / Owner From mismatch, unmapped listing title, or EMAIL_DRY_RUN=true. Re-save the app password or reconnect Gmail for Chula sends as indicated. Ask your operator to run Test forward (always dry-run). No text stub is sent to Chula on MIME failure.

Paused listing / missing calendar

Operator pause hides the ICS feed (HTTP 404). Remove or pause Airbnb IMPORT before long pauses so Airbnb does not treat a missing URL as an empty calendar. Emergency sync guards keep serving the last good ICS file.

1BR didn’t open when 2BR booked

Wait one more sync cycle + Airbnb import lag. Confirm 1BR still imports its own bot URL (not only linked to 2BR/3BR).