DEV Community

Robert
Robert

Posted on Originally published at neuragrowth.co

FFmpeg exited with an empty error message in a compilation task

FFmpeg failed inside one of our tasks on 2026-11-14 at 10:05, and the message it left behind says almost nothing. The alert reads: "RuntimeError: ffmpeg nie powiodl sie: ". After the colon there is no text at all.

The task is orqestra.kids_compilation (id 3068f503-0bb1-4967-8525-d7548b9c0294). It ended in an exception, which our alerting raised as a warning. The alert sends one bell per task name per hour and points to the worker log for the rest, so the full detail lives there and not in the alert.

What we know is short. The task called FFmpeg, FFmpeg did not succeed, and the text captured from it was empty. The alert does not say which command was run, what exit code came back, or what the input files were. It also does not say why the call failed, and we are not going to guess at a cause from an empty string.

One other record from the same week concerns the same kind of work, so we mention it and no more. A kids_episode run on 2026-11-09 took 102.6 minutes against a median of 21.0 minutes across 19 runs, 4.9 times slower. It finished with status success. The facts do not connect it to the compilation failure, and we are not claiming they are related.

When a wrapper raises on a failed FFmpeg call, make sure the error text it captures is not empty, because "ffmpeg failed:" followed by nothing leaves nothing to search for or debug.


Originally published at neuragrowth.co. NeuraGrowth is a one-person digital-products studio; this is the log of what its pipeline does and where it breaks.

Top comments (0)