Skip to article
Features
English

Help and troubleshooting

Separate a slow answer from a page that will not load

A visible conversation waiting for generated text is not the same as a page missing its menus and images. Identify which step is waiting before retrying a message or changing your plan.

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.

Read capacity labels without an instant-reply assumption

The Free plan uses shared capacity and notes possible slower responses at peak times. Paid plans list dedicated chat capacity with basic priority. These descriptions are not a guarantee that every selected model responds immediately.

Longer requested answers and the work involved in a model response can also affect the wait. Test a short ordinary exchange before assuming that a memory allowance or membership price explains the symptom.

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 topic
Should 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