When chat history gets too long, the interface starts lagging or freezing completely. Clear your browser cache and cookies first. If that doesn't help, start a new conversation instead of continuing an endless thread. The web version struggles with processing hundreds of messages at once. Consider using the mobile app for better performance with lengthy discussions.
The service hits capacity limits during peak hours, usually between 9 AM and 5 PM in US time zones. Wait 10-15 minutes and retry. Alternatively, switch from the web version to the mobile app, as they sometimes use different server pools. Paid subscribers get priority access, so free tier users experience this more often.
This happens when your session times out or loses connection. Don't refresh immediately or you'll lose the partial response. Wait 30 seconds, then click the regenerate button. If responses consistently cut off at the same length, you've hit the output token limit. Ask the system to continue from where it stopped.
Password reset emails can take up to 10 minutes to arrive. Check your spam folder before requesting another one. If you originally signed up through Google or Microsoft, you must use that same method every time. The system won't recognize email-password login for accounts created via social authentication. Disable browser extensions that block trackers, as they interfere with the authentication process.
The request went through but got stuck processing. Open developer console (F12) and check the network tab for failed requests. A 429 error means you're sending too many requests too quickly. Wait one minute between prompts. A 500 error indicates a server-side issue, so try again in a few minutes.