Skip to main content

Troubleshooting

"API request failed (Code: 401)"

Cause: Invalid or expired API key

Solution:

  1. Open Settings > AI Providers > [Your Provider]
  2. Check that the API key is entered correctly
  3. Click Validate button
  4. If validation fails:
    • Go to the provider's website (console.x.ai, platform.openai.com, etc.)
    • Check that your API key is still active
    • Check that you have available credits/billing set up
    • Generate a new API key if needed
  5. Enter the new key in Orion, validate again

"API request failed (Code: 429)"

Cause: Rate limit exceeded (too many requests too fast)

Solution:

  • Wait 30-60 seconds, then try again
  • Orion has client-side rate limiting, but providers have their own limits
  • Check your provider dashboard for rate limit info
  • Consider upgrading to a higher tier plan if you hit limits frequently

"Conversation chain expired on the server"

Cause: The xAI conversation chain expired (typically after extended periods of inactivity)

Solution:

  • This is handled automatically—Orion clears the stale conversation and starts fresh
  • Just resend your message
  • To prevent: Use "Clear server history" button in settings after long breaks

"The currently selected model does not support images"

Cause: You captured a screenshot but your current model doesn't support vision

Solution:

  1. Open Settings > AI Configuration > Model ID
  2. Select a vision-capable model:
    • xAI: grok-vision
    • OpenAI: GPT-4o, GPT-4 Turbo, GPT-4V
    • Anthropic: Claude Opus 4, Claude Sonnet 4.5, Claude 3.5 Sonnet, Claude Haiku 4
    • Google: Gemini Pro Vision, Gemini Pro 1.5, Gemini Flash 1.5
  3. Capture screenshot again
  4. Send your query

Right-click menu doesn't appear

Cause: "Enable Right-Click Menu" disabled in settings

Solution:

  1. Settings > Interface
  2. Check Enable Right-Click Menu (turn it ON)
  3. Restart editor (may be required)
  4. Right-click menu should now appear

Response is incomplete or cut off

Cause: Model hit max output token limit mid-response

Solution:

Option 1: Use Retry button

  1. Click Retry in the chat bottom bar
  2. AI may continue from where it stopped (works with some models)

Option 2: Increase token limit

  1. Settings > AI Configuration > Max Output Tokens
  2. Increase to 8000 or 16000 (or 0 for unlimited)
  3. Ask your question again

Option 3: Ask more focused questions

  • Instead of "Explain everything about Blueprints", ask "Explain Blueprint execution flow"
  • Narrow the scope to get complete answers

Chat window won't scroll to bottom

Cause: Manual scroll position is preserved by design (so you can read old messages while new ones arrive)

Solution:

  • Scroll to bottom manually — Auto-scroll re-enables when you're at the bottom
  • Send a new message — Auto-scroll re-enables on send
  • This is intentional behavior (not a bug)

"Failed to compile Blueprint"

Cause: Blueprint has errors, and "Compile On Send" is enabled

Solution:

  • This is actually helpful—the AI receives the compiler errors
  • Ask: "Why did compilation fail?" or "What are these errors?"
  • AI will diagnose based on the error messages
  • Fix the errors, send again

If you don't want auto-compilation:

  • Settings > Blueprint Context > Compile On Send (uncheck)

"Request timeout"

Cause: The AI provider took longer than the timeout setting to respond

Solution:

  1. Increase timeout: Settings > AI Configuration > Request Timeout (Seconds)
  2. Set to 90 or 120 seconds (default is 60-75 depending on model)
  3. Try again
  4. If timeouts persist:
    • Switch to a faster model (grok-code-fast-1, GPT-4o mini)
    • Reduce Blueprint/context size (send Selection instead of Full Graph)
    • Check your internet connection