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

ReaderUse this page when
First-time userA generation, video, provider, or Agent task failed
Support or success teamYou need a structured recovery table for a customer call
Technical operatorYou need to separate Redbit workflow state from provider, relay, browser, and Local Core issues

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

SymptomLikely causeChecksRecovery
Generation fails immediatelyMissing key, wrong endpoint, unsupported model variant, invalid input, or browser network/CORS issueSettings provider route, API key type, base URL, selected variant, card input requirements, provider consoleRe-enter Settings, choose a supported model, remove invalid references, retry one card before batch generation
Provider returns explicit errorProvider quota, billing, region, safety rejection, relay mapping, or payload mismatchProvider console, response message, relay capability warning, selected media type, payload requirementsFix provider account issue, reduce input complexity, switch route, or choose a supported relay model
Video is slow or appears stalledProvider queue, long duration, high resolution, first/last-frame processing, or polling delayDuration, resolution, variant, provider status, whether the card has a task ID or pending statusWait for provider polling, try shorter duration, lower resolution, fast variant, or another route with lower queue pressure
Seedance reference errorRequired first frame, last frame, or multi-reference input is missing or mixed incorrectlySelected Seedance mode, reference roles, prompt reference tokens, card validation messageUse text-to-video with no references, image-to-video with first frame, first/last with both endpoint frames, or multi-reference with at least one free reference
Model output is inconsistentDifferent model family, variant, safety filter, reference strength, prompt interpretation, or provider post-processingModel family, variant, ratio, seed or settings if available, source references, prompt changesCompare like-for-like settings, pin preferred outputs, tighten prompt/reference rules, and do not expect providers to match exactly
Model disappears after relay modeRelay capability filter does not include the family or variantRelay provider, custom relay model list, media type, Model Registry supportSwitch to direct provider, choose a relay-supported model, or add verified custom relay IDs
Agent says it finished but no media existsTool returned text only, generation failed inside a tool, target card was missing, or runtime lacks tool capabilityAgent tool transcript, normalized { success: boolean } result, created Cards, selected tab, capability profileAsk for explicit card creation/generation, run capability test, check card errors, or do the generation manually
Agent cannot complete taskRequest is ambiguous, destructive, external-effectful, or unsupported by current tools/runtimeOriginal request, target IDs, tool availability, confirmation requirements, Agent runtime profileNarrow the target, confirm risky action, choose a capable runtime, or split into manual steps
i18n or language display looks wrongLocale store mismatch, missing translation key, incorrect key path, or stale browser stateCurrent language setting, visible key text, related sibling translation keys, browser reloadSwitch language and reload, report exact key/path, avoid inline language branching in future UI edits
Assets disappear or cannot be selectedUnpinned recent asset cleanup, browser storage cleared, quota pressure, or project/global picker mismatchAsset Dock pinned state, SmartPicker mode, browser site data, project contextRe-import source asset, pin important outputs, switch picker scope, export important projects
Local Core feature does not respondLocal engine not running, pairing failed, blocked port, wrong binary, or feature not enabledLocal Core process, pairing code, local endpoint, browser/network errorsRestart trusted local engine, pair again, verify feature need, or use browser-only workflow
Export is missing expected filesWorkshop stage incomplete, output not generated, export mode mismatch, or unsupported package pathWorkshop project scenes, selected media, export mode, available generated assetsGenerate missing stage, select final assets, retry export, or hand off downloaded Card outputs

Escalation Packet

When support needs to investigate, include:
FieldInclude
Workflow surfaceCards, Series, Workshop, Agent, Seedance, Model Registry/Settings
RouteDirect provider, relay provider, custom relay, Local Core, or browser-only
Model selectionFamily, variant, ratio, duration, resolution, and Agent runtime profile if relevant
Input shapePrompt, file types, reference roles, and whether references came from upload, Asset Dock, or SmartPicker
Error evidenceCard error text, provider response summary, Agent tool result, browser console summary
Recovery already triedSettings update, retry, route switch, input simplification, Local Core restart, language reload

Next Step

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