Debug Render Failure
Use this skill when debugging render pipeline issues.
Environment
- •APP_RENDER_DRY_RUN=1 – Run full pipeline without paid APIs; outputs are placeholder files.
- •APP_DRY_RUN_FAIL_STEP=<step> – Simulate failure at a specific step. Valid steps:
tts_generate,asr_align,images_generate,captions_build,music_build,ffmpeg_render,finalize_artifacts. - •APP_DRY_RUN_STEP_DELAY_MS – Optional delay (ms) before each dry-run step.
Where to look
- •Run state:
Run.logsJson(array of log messages),Run.resumeStateJson(completed steps, resume data). DB via Prisma ordb:studio. - •Pipeline:
apps/server/src/services/render/renderPipeline.ts. CheckcompletedSteps,saveResumeState,handlePipelineError, and queue processing (processNextInQueue). - •Retry:
POST /api/run/:runId/retrysupports optionalfromStepto resume from a specific step.
Checks
- •Confirm Run status (
queued/running/failed/done/canceled/qa_failed). - •Inspect
logsJsonandresumeStateJsonfor the last completed step and error message. - •Reproduce with
APP_RENDER_DRY_RUN=1and optionallyAPP_DRY_RUN_FAIL_STEPto test error handling. - •Ensure FFmpeg is available when not in dry-run; check
ARTIFACTS_DIRand disk space.
References
- •renderPipeline.ts, run routes
- •.github/copilot-instructions.md (Test Modes, Debug render failures)