Use the failure point to choose your next check
| Problem observed | Relevant first checks |
|---|---|
| The website will not open at all | Connection and browser, followed by current incident announcements |
| No email code reaches the inbox | Entered address, spam filtering and the account's sign-in method |
| Picture generation fails while text still works | Access to the image feature and any image fair-use notice |
| A generated response is slow although the page works | Chosen model, generation queue and current service notices |
| Previous chats or the subscription are absent | The identity of the account that is signed in |
Preserve unsent text while testing the session
Retain your unsent message before refreshing the page once and testing the connection. Compare with a current browser, or try a normal window if a restricted session is the only place it fails. Do not clear site data until you know how to return to the account.
Give a request-limit notice time to clear instead of submitting the same request repeatedly. For Too many requests, follow the affected feature's cooldown guidance. Images have fair-use capacity separate from text, which can return as earlier usage leaves the recent activity period.
Follow announcements and report unexplained errors
We post incident information and progress in community announcements. Read the dates and latest update, rather than relying on an older discussion. A failure confined to one device may not affect everyone else using the service.
If no announcement explains what you see, report the device, browser, affected feature and exact message, together with the time and time zone. A screenshot can help after sensitive details are removed. Keep login codes, complete card information and unrelated private dialogue out of the report.
Questions
Where can I check whether an incident explains my error?
Read the current community incident announcements and their most recent updates. If they do not cover the problem, identify which feature fails, try the relevant account or connection checks and send support the symptom.
Why might images be limited when text chat still works?
Image generation has its own fair-use controls based on recent activity, with capacity returning automatically. A Too many requests message for an image does not necessarily mean text chat is unavailable.