Check what has already loaded
If the library, profile and previous messages display normally, focus on the selected model and current conversation. If several pages and images fail together, compare the browser and connection first.
Keep a copy of the text you are composing before refreshing. Sending the same message repeatedly can create uncertainty about which request a later answer belongs to, without addressing the original delay.
Retry once you know what you are preserving
Check whether another public page works and whether the intended account remains open. If the issue follows a purchase, keep the receipt and confirm its status rather than buying again to test access.
For a recurring delay, record the model, time and exact message for support. Do not use queue-jumping scripts, share an account token or remove security controls in response to an unverified shortcut.
Common questions
Why might Free access slow down at a busy time?
Shared capacity can contribute to a delay, but a connection fault, model workload or requested answer size can also matter. Check the specific step that is waiting.
More on this topicDoes purchasing priority guarantee an immediate response?
No. The paid plans describe capacity priority rather than a fixed response-time commitment for every model and situation.
More on this topicShould I keep sending the message while it waits?
Preserve the text and check the fault instead of repeatedly submitting duplicates. Keep an exact error and approximate time if the problem persists.
More on this topic