Skip to article
Features
English

Help and troubleshooting

Loading, slow replies and queues

A page that never opens and a model that is still preparing a response are different problems. We separate page loading, conversation capacity and account access before suggesting a change.

Identify the step that is waiting

If the library and profile load but a reply takes time, check the selected model and the state of that conversation. If images, menus and several pages all fail, begin with the browser and connection instead.

Avoid sending the same message repeatedly while a response is pending. Duplicate requests can make it harder to understand which reply belongs to which turn.

Understand shared and dedicated capacity

The Free plan lists shared chat capacity, with the possibility of slower responses at peak times. Paid plans list dedicated capacity with basic priority. Neither label is a guarantee that every model will respond instantly.

A model's generation work and the length of the requested reply can also affect how a conversation feels. Test a short normal exchange before assuming a longer plan allowance is the cause of the delay.

Retry without losing the scene

Keep a copy of the message you were writing before refreshing. Check a second public page and confirm the intended account is still open. If a purchase is involved, keep the receipt rather than buying again immediately.

For a persistent queue or loading error, note the model, approximate time and exact message for support. Do not disable browser security or use account scripts from an unknown source to try to move ahead of a queue.

Questions and answers

Why is CrushOn AI slow during high traffic?

Shared capacity can affect Free access at busy times. Model selection, reply length and connection problems can also cause delays, so check the step that is actually waiting.

More on this topic
Should I keep refreshing or resending?

Keep a copy of your message and refresh carefully rather than sending duplicates. Note the exact error if the problem continues.

More on this topic