Troubleshooting

Fixes for the most common issues.

• Snipe shows as rate-limited — Resy is temporarily throttling requests. SnipeSeats backs off automatically and retries; the connectivity banner shows exactly when it'll try again.
• Banner says it can't reach the platform through your proxy — your proxy is either unreachable or rejecting the credentials SnipeSeats is sending it. Re-test the proxy under Accounts & proxies; if it's an authentication error specifically, the banner calls that out separately from a general connection failure.
• Banner says the platform is taking too long to respond — a timeout, distinct from rate-limiting: the request went out but nothing came back in time. Usually resolves on its own; persistent timeouts are often a slow or overloaded proxy.
• Account won't connect — double-check the email and password match your Resy login exactly, and that any attached proxy is reachable.
• Clicked “Sync venues” and got zero results — Sync venues pulls venues within about 10 miles of your current location (detected automatically from your IP), so it only ever returns nearby restaurants. If the one you want is further out — or your IP-based location is off, which VPNs and proxies can cause — the sync won't pick it up. Search for the restaurant by name in the Venues search bar instead: a name search isn't limited by distance, so it'll find it regardless of location.
• Not getting Discord notifications — each event (booking success, payment failed, payment missing, snipe expired, proxy unhealthy, auth failed) has its own toggle and its own webhook URL under Preferences & notifications. Turning one event on doesn't turn the others on — double-check the specific event you expected is both toggled on and has a webhook saved.
• Accidentally cancelled a booking — there's no undo. Cancelling in SnipeSeats calls Resy's own cancel endpoint with the token issued when the reservation was booked, so it cancels the real reservation on Resy, not just the local record. If you didn't mean to, you'll need to try and re-book it (as a new snipe, or directly on Resy) like any other open table.
• Custom polling window times look off — window start/end times (under Setting intervals) are in the venue's local timezone, not yours. If you're booking somewhere in a different timezone than you're in, account for the offset when picking your windows.
• My snipe stopped progressing overnight — SnipeSeats only works while it's actually running: your computer needs to stay awake and connected to the internet the whole time, since there's no cloud server backing it up. It automatically prevents sleep while open (see Keeping your computer awake), but closing a MacBook or Windows laptop's lid will still sleep it — Linux is the exception, where lid-close is inhibited too — and a dead battery or dropped Wi-Fi will pause monitoring regardless of platform. Keep the laptop open (or on an external display), plugged in, and connected if you're relying on a snipe unattended.
• App won't open on macOS — see the Gatekeeper note under Installation.

If none of the above fixes it, reach out — see Support.