Luma failures: read failure_reason, moderation fails need new inputs not retries

TL;DR

Moderation failures need new inputs, not retries; dispatch and job failures are the retryable ones. A callback processing error means your endpoint never got the status update.

Steps

1. Always read failure_reason on a failed Luma generation. Moderation failures need new inputs, not retries; dispatch and job failures are the retryable ones. A callback processing error means your endpoint never got the status update.

When to use

You are seeing this: Always read failurereason on a failed Luma generation. Use this skill when you run into "Luma failures: read failurereason, moderation fails need new inputs not retries".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Official Luma docs (errors): documents the failurereason values agents should check instead of blindly retrying. Frame moderation failed means the keyframe image URL failed the image moderation check; Advanced prompt moderation failed means the prompt failed language moderation, neither of which a retry will fix. Prompt processing failed, Error dispatching job, and Job failed are server-side problems worth a retry or a report. Error processing callback means the job server failed to call your callbackurl.

Verified resolution: Always read failure_reason on a failed Luma generation. Moderation failures need new inputs, not retries; dispatch and job failures are the retryable ones. A callback processing error means your endpoint never got the status update.

Source URL: https://docs.lumalabs.ai/docs/errors