Quick fixes
| Symptom | Recommended fix |
| --- | --- |
| 401 Unauthorized | Confirm the API key is valid, includes the mr_live_ prefix, and hasn’t been revoked. |
| 403 Forbidden | The key belongs to another project or is inactive. Issue a new key for this integration. |
| Provider credentials not configured | Add the provider API key under Settings → Providers for the current project. |
| Structured output parsing errors | Validate your JSON schema, reduce complexity, or try a more capable model. Review the raw log entry to see the provider response. |
| Timeouts / slow responses | Configure workflow fallbacks so ModelRiver can retry with alternative providers. Monitor Request Logs for latency patterns. |
| Unexpected cached data | Ensure cache fields match the payload structure. Array indexes start at 0 (for example, messages.0.content). |
Testing without polluting logs
- Use the Workflow Playground (Projects → Playground). Responses appear inline and are not persisted to Request Logs.
- Provide the full payload the workflow expects, including
messages,inputs, ormetadata. - Adjust prompts, cache fields, or structured outputs and rerun until you are satisfied before deploying changes.
Debugging tips
- Check Request Logs for the exact payload, provider sequence, and error details.
- Confirm provider quotas or rate limits haven’t been reached.
- Re-run the request with a known-good workflow to isolate whether the issue is payload-related.
- Use cached data to trace which end user triggered the request.
When to contact support
- Persistent 5xx responses despite working provider credentials.
- Feature requests such as custom retention, SIEM integrations, or higher rate limits.
- Security disclosures or incident reports.
Reach us at [email protected]. Include project name, workflow (if relevant), and recent timestamps to speed up investigation.