Workflow Issues
Workflow seems stuck
- Check if paused — Look for pause indicator in chat
- Check approval mode — Manual mode waits for approval on each tool
- Cancel and retry — Press
Cmd+.or click stop, then try a different approach - Branch from earlier — Click branch icon on any message to start fresh
AI responses are slow
- Check your API provider’s status page
- Try a smaller/faster model
- Check rate limits haven’t been exceeded
- Verify stable internet connection
Workflow fails repeatedly
Reliant pauses instead of crashing. Check the error message, fix the issue (permissions, network, API), then click resume.Application Issues
Something not working right
Reinstall Reliant:App won’t start
- Check if another instance is running
- Try launching from terminal to see errors
- Reset app data (see above)
- Reinstall from scratch
API Issues
”Invalid API key” error
- Verify key is correct (no extra spaces)
- Check key hasn’t expired or been revoked
- Test in provider’s dashboard/playground
- Try regenerating the key
Rate limit errors
- Wait a few minutes and retry
- Switch to a different model
- Check your plan’s limits with the provider
Logs
Logs help diagnose issues. Find them at:| Platform | Location |
|---|---|
| macOS | ~/Library/Logs/Reliant/ |
| Linux | ~/.local/share/reliant/logs/ |
| Windows | %APPDATA%\Reliant\logs\ |
reliant.log for recent activity. Logs rotate to prevent large files.
Known Issues
Chat gets into a bad state
Occasionally a chat may get into an inconsistent state (agent confused, repeated errors, or unexpected behavior). Fix: Branch from an earlier message where things were working. Click the branch icon on any message to start a fresh conversation from that point.Refresh doesn’t work (macOS)
Cmd+R to refresh the page is currently disabled in the packaged app. This is intentional to prevent accidental data loss.
Workaround: Close and reopen the tab, or restart the app if needed.
Auto-updater may fail to open new version
After downloading an update, you may see “The application ‘Reliant’ can’t be opened.” This happens when background processes from the previous version are still running. Workaround:Local model loading is broken
Local model loading (e.g., Ollama, LM Studio) is currently not working. We’re aware of the issue and working on a fix. In the meantime, please use cloud-based API providers.Get Help
Still stuck? Email support@reliantlabs.io with:- Reliant version (Help → About)
- What you were trying to do
- What happened instead
- Relevant log snippets
See also: FAQ • Feedback & Support