Improved October 10, 2026

See render notes on the job page

See what a render changed from what you wrote, on the job page: fonts that fell back, clips held past their file, and clips that crossfaded over an overlap.

Dashboard

A render can finish complete and still not be exactly what you wrote. A font the render could not supply falls back to another, a clip that runs past its file holds its last frame, and two clips that overlap on one track crossfade. The job response has carried those notes in the render step for a while, under fontFallbacks, clipOverruns and clipOverlaps. The dashboard did not show them.

It does now. Open a job, and each note sits under the step that produced it, in the Steps section, in the words the runner wrote. Nothing to turn on, and jobs that rendered exactly as written look the same as before.

The Steps section of a compose job: Download inputs, Translate to execution plan, Execute render engine, Upload output. Under the render step, three notes: a font that was not available and fell to the next entry, a music bed that ran 12 seconds past its file, and a clip that started one second before the previous clip ended so the two crossfaded. — The Steps section of a compose job that finished complete. Under the render step, a font fell back, a music bed ran 12 seconds past its file, and two clips crossfaded over a one-second overlap. Each note ends with the change that makes it go away.

The same lists are in GET /jobs/:id under each step’s meta, for code that wants to check them. See the compose docs for what each note means and how to change the timeline so it does not appear.