Skip to main content

Troubleshooting Playbook

Use this page when a workflow fails after the user has chosen a Redbit surface and provider route. Start with the visible symptom, then check route, model, input, storage, and Agent/runtime boundaries.

Who Should Read This

Before You Troubleshoot

Capture the card or Agent error, selected model family and variant, direct provider or relay route, input references, browser console error if available, and whether Local Core was paired. Do not paste real API keys into support notes.

Troubleshooting Table

Escalation Packet

When support needs to investigate, include:

Next Step

For security-sensitive issues, use Security and Credentials. For Seedance-specific reference rules, use Seedance Video Workflows.