Help

Support

Start with these steps when Twitch will not connect, a flag will not update, or an API request returns an error.

Managing your flag

  1. Twitch will not connect

    • Return to the home page and choose Connect Twitch again.
    • Make sure your browser allows the first-party twitchflags_session cookie.
    • If an old session appears stuck, sign out, refresh the page, and connect again.

  2. The flag will not load

    • Refresh the page once.
    • Confirm the page shows the Twitch login you expect.
    • If the identity is missing or incorrect, sign out and reconnect your Twitch account.
    • If the error continues, wait briefly and try again.

  3. The flag will not save or remove

    • Choose a country or territory before saving.
    • Wait for the current request to finish before trying again.
    • After repeated attempts, wait at least one minute before retrying because changes are rate limited.
    • Refresh once to confirm whether the change was already applied.

  4. A supported client still shows the old flag

    Browsers may cache flag reads for one week. Shared edge caches may retain them for the same period and reuse stale responses while revalidating. Twitch Flags invalidates its Vercel cache entry after a successful change, but it cannot clear a copy already held by a browser, independent client, or intermediary.

Using the API

See the API documentation for the complete endpoint, response, CORS, and caching contract.

400 invalid_twitch_user_id
Use a digits-only Twitch numeric user ID.
404 flag_not_set
The ID is valid, but no flag mapping is currently available.
429 rate_limited
Reduce request frequency, cache responses, avoid tight retry loops, and wait for the one-minute request window before retrying.
503 service_unavailable
A dependency is temporarily unavailable. Retry later with bounded backoff.

Public GET responses allow cross-origin reads. Use OPTIONS when a client needs a preflight request.

Contact

If these steps do not help, contact the operator through desertice.link (opens in new tab). Include:

  • the Twitch login or numeric Twitch user ID involved;
  • the request URL and HTTP status for an API issue;
  • the approximate UTC time of the failure;
  • your browser or client name and the steps already tried.

Never send passwords, OAuth tokens, session cookies, Redis credentials, Arcjet keys, or other secrets.