Docs

Unblock your team fast

Use this checklist to resolve authentication problems, provider errors, and unexpected responses.

Current section

Troubleshooting

Updated

This week

Build time

Minutes, not hours

Quick fixes

SymptomRecommended fix
401 UnauthorizedConfirm the API key is valid, includes the mr_live_ prefix, and hasn’t been revoked.
403 ForbiddenThe key belongs to another project or is inactive. Issue a new key for this integration.
Provider credentials not configuredAdd the provider API key under Settings → Providers for the current project.
Structured output parsing errorsValidate your JSON schema, reduce complexity, or try a more capable model. Review the raw log entry to see the provider response.
Timeouts / slow responsesConfigure workflow fallbacks so ModelRiver can retry with alternative providers. Monitor Request Logs for latency patterns.
Unexpected cached dataEnsure 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, or metadata.
  • Adjust prompts, cache fields, or structured outputs and rerun until you are satisfied before deploying changes.

Debugging tips

  1. Check Request Logs for the exact payload, provider sequence, and error details. The timeline view shows the complete request lifecycle, including failed provider attempts, webhook deliveries, and callbacks.
  2. Confirm provider quotas or rate limits haven't been reached.
  3. Re-run the request with a known-good workflow to isolate whether the issue is payload-related.
  4. Use cached data to trace which end user triggered the request.

For comprehensive guidance on using Request Logs for debugging, see the Request Logs documentation.

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.