Add the MCP server ▸
Troubleshooting4 of 6 ▾

Support/Troubleshooting

A render failed

A failed render isn’t charged: open the brand’s Media tab and choose Retry under Recent renders, which starts a new render from the same brief.

TroubleshootingUpdated 9 Nov 2026·3 steps

What you’ll see

  • A message: “Your Reel didn’t render, so it isn’t charged.”, often with what Motionpad said.
  • Or an email, “Your Reel didn’t render”, if you weren’t in the app.
  • Under Recent renders in the brand’s Media tab: Didn’t render, with the reason and not charged.

Fixes

  1. Try it again

    Open Brands, choose the brand, then Media. Under Recent renders, choose Retry. It’s a new render from the same brief, so it uses one, but it goes without the brief’s images.

  2. If it didn’t start at all

    A render that’s refused before it starts says why:

    • “Another render is starting right now. Start this one in a moment.” Wait a moment and ask again.
    • “This month’s renders are used up…” Raise Extra renders in Settings → Plan, or choose a plan if you’re on the trial.
    • “…extra renders wait until the last payment goes through.” Update your card under Manage billing.
  3. Ask with a new brief

    If it fails again, ask your assistant for a new render with a shorter, plainer brief.

From the CLI, find the render and try it again:

syndera renders ls --days 7

Then syndera renders retry <render-id>.

Still stuck?

Write to hello@ketryon.com with the brand, when you asked for it, and what Motionpad said. Settings → Account → Get help opens an email with your account filled in.

Was this helpful?