Your results

What a finished job hands you, how to get it, and the one deadline worth knowing about.

What a job produces

Output	What it is
`Highlight reel`	One per selected profile, at the length you asked for, with your teaser intro and branding if you enabled them.
`Vertical shorts`	1080x1920 clips with burned-in captions and optional title cards, framed the way you chose.
`Thumbnails`	Cover frames for the reel and for each short.
`Metadata`	Generated title, description, tags and chapter markers, in your chosen metadata language, ready to paste when you upload.
`Caption files`	A plain .srt sidecar for every short, whether or not captions were burned in, so a wrong line can be fixed without re-rendering.

If you selected more than one highlight profile, you get a complete set per profile, each labelled with the profile that produced it.

Downloading

Open the job to download files individually, which is what you want when you are posting one short at a time. There is also a single ZIP of everything, built on demand when you ask for it rather than stored permanently.

Download links are time-limited. If a link has gone stale, reload the job page and it will hand you a fresh one. If you are automating this, request the results endpoint again instead of caching URLs; see the API reference.

How long files are kept

Output files are deleted after about 30 days. Roughly 30 days after a job last changed, its videos, thumbnails, metadata and caption files are permanently removed from storage. The job stays in your history with its settings and stats, but the files are gone and cannot be recovered. Re-running the job would cost credits again.

In practice this is rarely a problem, because most people download what they want within a day or two. It becomes a problem when a job is treated as an archive. If you need long-term copies, pull them into your own storage. Wiring a webhook to download automatically when a job completes is the reliable way to do that.

Job states

State	What it means
`pending`	Queued, waiting for a free machine.
`running`	Being processed.
`completed`	Finished. Files are ready.
`failed`	Stopped without producing output, and credits were refunded. Cancelling also lands here, labelled as cancelled by user; there is no separate cancelled state.

A failed job refunds automatically. If it failed because the VOD was unusable, the message says so directly rather than giving you a generic error, so you know whether to fix the link or try a different stream.

When the picks were not right

Rate the job. This is not a satisfaction survey that disappears into a spreadsheet: the rating and reason feed the scoring system that chooses moments, so it changes what future jobs pick.

Reason	Use it when
`Wrong moments`	It clipped things that were not the good parts.
`Timing off`	The right moments, but starting or ending in the wrong place.
`Needs editing`	Usable, but not something you would post as-is.
`Something else`	Anything the other three do not cover. This one asks you to write what went wrong, because an unexplained complaint is not something anyone can act on.

You can also rerun a job, which opens a new one prefilled with the same settings. That is the quick way to change one thing, a longer clip minimum or a different profile, without re-entering everything.

Cancelling a job

A pending or running job can be cancelled, and credits come back on a tiered basis: the further it got before you stopped it, the less is refunded, because the work was already done. A job that has already completed cannot be cancelled.

Exact refund behaviour is covered in Credits and plans.