Common timeout errors
Request timeout
Request timeout
Error: “Request timed out” or “Model took too long to respond”Causes:
- Very long or complex prompts
- Model provider experiencing high load
- Network connectivity issues
- Context window limits exceeded
- Simplify your prompt: Break complex requests into smaller parts
- Reduce context: Remove unnecessary conversation history
- Try again: Temporary provider issues often resolve quickly
- Switch models: Try a faster model (GPT-4o-mini, Claude Haiku)
- Check network: Verify stable internet connection
Connection error
Connection error
Error: “Connection lost” or “Failed to connect”Solutions:
- Check internet connection
- Disable VPN temporarily
- Try different network
- Clear browser cache
- Disable browser extensions
- Try incognito/private mode
Rate limit exceeded
Rate limit exceeded
Error: “Too many requests” or “Rate limit exceeded”Causes:
- Sending requests too quickly
- Reached usage limits for your plan
- Provider-side rate limiting
- Wait a moment before retrying
- Reduce request frequency
- Check your subscription plan
- Upgrade for higher limits if needed
Preventing timeouts
1
Optimize prompt length
- Keep prompts concise but clear
- Remove redundant information
- Use structured prompting
2
Manage context
- Start new conversations for unrelated topics
- Clear old conversation history
- Use Memory instead of repeating context
3
Choose appropriate models
- Use faster models for simple tasks
- Reserve powerful models for complex problems
- See model comparison
4
Monitor usage
- Track your usage patterns
- Stay within plan limits
- Upgrade if regularly hitting limits

