Debug failed recordings

Most failed recordings come from one of four things: the page could not load, the prompt was too vague, the flow required state the recorder did not have, or the selected style did not match the page.

First checks

1. Open the target URL in a clean browser profile.
2. Confirm the page loads without manual login, cookie banners, or local-only data.
3. Try a shorter prompt with one task and one finish line.
4. Use plain-scroll to confirm the recorder can capture the page at all.

bash
littledemo demos create \  --project proj_abc123 \  --prompt "Scroll through the page from top to bottom" \  --template plain-scroll

If the output wanders

Use a more specific prompt:

text
Focus only on the pricing table. Show the monthly and annual toggle, then stop on the Pro plan.

Or add a template:

bash
--template pricing-focus

If the page needs app state

Use a stable demo environment with seeded data. Avoid flows that require one-time codes, private inboxes, or a human approving another device.

If the demo is close

Restyle it instead of regenerating:

bash
curl -X POST https://littledemo.com/api/v1/demos/demo_abc123/restyle \  -H "Authorization: Bearer ld_live_xxx" \  -H "Content-Type: application/json" \  -d '{ "presentation": { "recordingTemplate": { "id": "cinematic" } } }'