Troubleshooting
Common issues and solutions for The One AI Platform.
Jarvis Not Responding
Symptoms: Jarvis chat shows a loading spinner or returns an error.
Solutions:
- Check your AI Platform subscription is active in Hub Billing
- Verify your usage quota hasn't been exceeded for the current period
- The upstream AI provider may be experiencing an outage — check the status page
- Try refreshing the page and starting a new conversation
Custom Agent Not Working as Expected
Symptoms: A custom agent returns irrelevant or incorrect responses.
Solutions:
- Review the agent's system prompt — ensure it has clear instructions and context
- Check the knowledge base attached to the agent — missing or outdated documents affect quality
- Try a different model — some models perform better for specific tasks
- Test with simpler prompts first to isolate the issue
Usage Quota Exceeded
Symptoms: AI features return "quota exceeded" errors.
Solutions:
- Check current usage in Settings → Usage Quotas
- Wait for the quota period to reset (monthly by default)
- Increase the quota limit in Settings if needed
- Review usage analytics to identify which team or agent is consuming the most
Prompt Template Not Producing Expected Output
Symptoms: A prompt template generates inconsistent or incorrect results.
Solutions:
- Review variable placeholders — ensure all
{{variables}}have values at runtime - Test the template with the Preview function before deploying
- Add more specific instructions to the template's system context
- Check the model selection — ensure the template uses an appropriate model for the task
Studio App Build Errors
Symptoms: A Studio app won't publish or shows errors in the builder.
Solutions:
- Check for disconnected blocks — all blocks must be connected in the flow
- Verify required configuration on each block (API keys, model selection, field mappings)
- Test the app in preview mode to see specific error messages
- Check that integration blocks have valid credentials
AI Gateway Rate Limiting
Symptoms: Requests are being throttled or returning 429 errors.
Solutions:
- Check your tier's rate limits in Settings → Usage Quotas
- Spread requests over time if running batch operations
- Use the queue system for high-volume operations instead of direct API calls
- Contact support if your usage patterns require higher rate limits
ℹ️If you encounter an issue not listed here, contact support with the conversation ID (for Jarvis), agent ID (for custom agents), or app ID (for Studio apps).
Next Steps
- Getting Started — Initial setup and configuration
- Usage Quotas — Managing AI consumption limits
- Governance — AI policy configuration