When Something Goes Wrong

Most problems with this app fall into a handful of patterns, all of them seen before and recorded in the project’s own notes. Work down this page in order.

First check: is the server up?

The app has a health address that answers instantly when the server is running.

What you do

1. Open a web browser.
2. Go to https://booking.amapas353.com/health
3. If you see {"status":"ok"} — the server is fine; the problem is elsewhere on this page.
4. If you see an error page instead, the server process is down. This usually rights itself; if it does not, whoever has access to the Railway dashboard (the hosting service) can read the deploy logs and trigger a redeploy there.

The booking card is blank in ChatGPT

A quirk recorded in the project’s notes: the card has been seen coming up blank on a first load and appearing after a page refresh — a caching issue on ChatGPT’s side, not a fault in the app.

What you do

1. Refresh the ChatGPT page and ask again in a fresh chat.
2. If it is still blank, open https://booking.amapas353.com/widget in a plain browser. If the booking screen works there, the problem is on ChatGPT’s side or in the app’s ChatGPT configuration — that needs whoever maintains the code, not you.

A guest says their dates won’t select

Crossed-out dates in the calendar mean those dates are blocked in Lodgify — either by an existing reservation (including forgotten Tentative test requests) or by an owner block.

What you do

1. Open the Lodgify calendar for the property.
2. Look at the dates in question for a reservation or a closed period.
3. Remove whatever should not be there (decline stale Tentative requests, lift outdated blocks). The app follows the Lodgify calendar automatically.

A request was refused with “Minimum stay”

Working as designed: the property has a 3-night minimum, enforced both on the screen and again on the server. Nothing was filed in Lodgify. The guest should pick a longer stay.

No emails are arriving

Emails (guest confirmation and owner notification) are sent only if the email settings are configured on the server; those settings live as environment variables in the Railway dashboard. Two important facts:

• A missing email does not mean the request was lost — the reservation is created in Lodgify regardless. Check Lodgify first.
• If email settings were never filled in, or the password changed, emails stop silently. Whoever has Railway access can check that the email variables are set there.

The price looks like a flat rate when it shouldn’t be

If the live rate lookup fails, the app deliberately falls back to a base nightly rate of $250 — still adding the $65 cleaning fee and both taxes — rather than showing nothing. If quotes look suspiciously uniform across seasons, the rate lookup may be failing; that is a job for whoever maintains the code. The guest is never undercharged fees or taxes by this fallback.

Rules of thumb before touching anything technical

Two hard-won rules from the project’s records, for anyone tempted to make changes:

• The two tool names and the app’s registered details are frozen. They were approved by OpenAI as part of publishing the app; renaming or editing them breaks the published app and forces a re-review. Behavioural fixes inside the server are fine; anything touching the app’s registered metadata needs a planned resubmission.
• Code changes deploy automatically. Any change pushed to the main branch of the GitHub repository rebuilds and redeploys the live server within a couple of minutes. There is no separate “publish” step — so nothing gets pushed casually.

If a problem does not fit anything on this page, gather three things before asking for help: what the guest saw (a screenshot of the card), the date and time, and whether https://booking.amapas353.com/health answered ok. Those three answers cut the diagnosis in half.