Troubleshooting
1. I'm not getting reservation alert emails
Cause: incorrect settings in email_settings.
Fix:
- Settings → Email notifications → "Notify when someone reserves" is checked.
- "Alert emails" has at least one valid email.
- Create a test reservation from the public website. If it doesn't arrive within 2 minutes, contact support.
2. The customer doesn't get the confirmation email
Cause: empty or blocked customer_email field.
Fix:
- On the reservation, check the customer's email is correct.
- In Settings → Email → "Reservation confirmation" is on.
- Ask the customer to check spam or promotions.
- If they have
email_unsubscribesactive, they won't receive anything.
3. The public page says "Restaurant not found"
Cause: wrong slug, restaurant inactive, workspace inactive.
Fix:
- Check the URL:
/c/your-slug(no spaces or accents). - In Settings → Identity verify the restaurant is active.
- If you changed the slug, update QR, embeds, and shared links.
- Try in incognito (without a session).
4. My session ends too soon
Cause: refresh token expires (~7 days), private browsing, another device logged out.
Fix:
- Log in again.
- Avoid incognito mode for regular use.
- Interact with the app every 5-6 days if you want to stay logged in.
- Clear the cache if problems persist.
5. Slots don't show as available
Cause: incomplete configuration.
Fix:
- Settings → Hours: there are slots for those days.
- Settings → Tables: there are active tables with capacity >0 (Tables mode) or
cover_capacity>0 (Covers mode). - Check there's no service pause active.
- The date is within the configured
booking_window.
6. Payment error / Stripe portal won't open
Cause: timeout, expired Stripe session.
Fix:
- Retry in 1-2 minutes.
- Sign out of Stripe (other tab) and try again.
- Check your payment method at dashboard.stripe.com.
- Clear the browser cache.
7. The embed shows clipped on my site
Cause: insufficient height.
Fix:
- Bump
height="900"(mobile) or usemin-height: 720pxon the container. - Ensure
width: 100%isn't restricted by parent CSS. - More detail in Embed iframe.
8. Customers say the QR doesn't work
Cause: slug changed, restaurant inactive, bad print.
Fix:
- Re-generate the QR from Settings → Reservations → QR.
- Print at minimum 5x5 cm with good resolution (>=300 DPI).
- If you changed the slug, old QRs don't work - reprint.
9. I don't see the Pinche button
Cause: your plan doesn't include AI.
Fix:
- Pinche is on the Advanced and Elite plans.
- Check your plan in Settings → Subscription.
- Reload the page (Ctrl+F5).
10. Pinche doesn't reply or errors out
Cause: Gemini timeout, rate limit, context too large.
Fix:
- Retry in 1-2 minutes.
- Split long prompts into shorter ones.
- Reload the page.
- If it persists, report with the exact error message.
11. I lose changes when switching screens
Cause: you forgot to save.
Fix:
- Click Save and wait for the green toast before navigating.
- If you see "You have unsaved changes", confirm save.
12. The menu doesn't update for the customer
Cause: cache.
Fix:
- Wait up to 5 min (Supabase cache).
- Ask the customer to reload with
Ctrl+Shift+R(ignores local cache). - On mobile, close and reopen the browser app.
13. "Access denied" error
Cause: expired session, insufficient role, restaurant in another workspace.
Fix:
- Sign out and sign in again.
- If you have several workspaces, check the switcher to confirm you're on the right one.
- If you're staff and need access to something admin, ask the owner for promotion.
14. Tables don't reserve correctly / capacity conflicts
Cause: misconfigured tables or reservations with inconsistent data.
Fix:
- On the floor plan: each table with capacity >0 and Active state.
- Try deactivating/reactivating the specific table.
- In the reservation list, sort by date and check overlaps.
- If you see "no availability" but you have free tables, contact support with a screenshot.
15. Changes to hours or tables don't show publicly
Cause: CDN or browser cache.
Fix:
- Wait 2-5 minutes.
- Open the public page in incognito.
- If you still don't see the change after 10 min: contact support with the exact timestamp of the change.
Reporting an issue
When you contact support, include:
- Your account email
- Workspace / restaurant name
- Approximate timestamp
- Screenshot of the error (if applicable)
- Reproduction steps
- If intermittent: how often it happens
Email: support@restapro.es. We reply within 24 h.