Render Queue
A combination package is one cell of the matrix made real: a single template filled with one valid combination of catalogue items. You create combination packages by expanding a campaign, and the Render Queue is where you watch every one of them across your Organization on its way to a Final Video.
Expanding a campaign
Expansion walks the campaign's matrix and creates one combination package per valid combination. Two things make it safe to run often:
- It is idempotent. Each combination package has a deterministic key built from its template, format, and the exact set of catalogue items. Re-expanding updates what is there and adds only what is new, never duplicating.
- It respects the freeze rule. If you change the matrix later and a combination drops out, a combination package that is still being configured is pruned, but a combination package that has already moved forward is kept as a deliverable.
Expansion reports back what it did: how many combination packages it created, kept, pruned, and retained because they were frozen.
Freeze-at-render
This is the rule worth internalising. A combination package that is still configuring tracks the latest template and matrix. Once a combination package is rendered, its output is frozen and upstream edits never silently change it. Re-expanding the campaign leaves a frozen combination package exactly where it is. Producing a new output is always a deliberate act, never a side effect of editing the brief.
Stale cells
Changing the template or an axis changes what a combination is, so cells built under the old shape can no longer be produced by the current matrix. The freeze rule keeps them (they are past configuring), but they cannot render either, because the matrix no longer carries the items they were built from.
Klyo marks these stale: the Render matrix step shows the count above the table and a badge on each affected row, and one confirmed action discards the whole set. Discarding retires the cells rather than erasing them, so anything that was already measured or attributed keeps its history. A released cell is never stale and can never be discarded this way, since hiding a live creative from the console would not stop it running. If the matrix later produces the same combination again, re-expanding brings the cell back where it left off.
The Render Queue list
The Render Queue is a filterable table across your Organization. You can filter by campaign and by status, turn on Hide rendered to narrow the list to cells still needing work (configuring, rendering, rejected, or needs attention), and page through the results. Each row shows the status, the format, and the campaign it belongs to, a live one-line note on what is happening ("Generating the clip this render composes.", "Rendering...", "Rendered in 42s"), and a Render (or Re-render) action, so you can trigger or retry a single cell without opening the campaign. A row opens a detail dialog with the full catalogue item set, the template, and a link back to the campaign.
Status
A combination package carries a status that describes where it is in its life:
| Status | Meaning |
|---|---|
| To render | Not yet rendered, still tracks the matrix |
| Rendering | Render in progress |
| Rendered | Output produced and frozen |
| In review | Awaiting human approval |
| Approved | Cleared to go live |
| Rejected | Reviewed and turned down, excluded from activation |
| Activating | Being pushed to a channel |
| Activated | Uploaded to its channel; a YouTube upload stays unlisted until you set visibility in Studio |
| Needs verification | A push finished ambiguously; confirm it or return it to the queue |
| Handed off | Exported in a Google Ads or DV360 pack to finish by hand |
| Needs attention | Something failed and a human should look |
Status today
Expanding a campaign creates combination packages in configuring. From there the app drives them forward: a render moves a cell to rendering, then in review on success or needs attention on failure, and reviewing it records approved or rejected, one cell or in bulk. Activation drives the rest: pushing an approved cell to a channel records activating then activated (uploaded to its channel; a YouTube upload stays unlisted until you set its visibility in YouTube Studio), or a handoff marks it handed off. An approved cell can also be hosted first: its video uploaded to YouTube unlisted with nothing released, marked with a Hosted badge while it stays approved, so a later activate reuses the banked upload instead of uploading again (see Hosting).
When a push finishes ambiguously, an upload that may or may not have completed, or a process that died mid-push, the cell holds in an amber Needs verification state instead of claiming success, so a paid upload is never blindly repeated. Resolve it three ways: confirm live after you check the video is on the channel in YouTube Studio (records the id you verified and moves the cell to activated), record it as hosted if the upload was a host and you are keeping it banked for reuse (record the YouTube video id so a later activate reuses it), or return to queue for a fresh push (which accepts the risk of a duplicate upload if the first one did land). See Generation and render and Activation.
Reviewing across campaigns
The Review console (a separate area in the left navigation) is where you watch each Final Video and approve, reject, or re-render it. It spans every campaign in your Organization: a filterable, sortable queue on one side, and the video with its detail on the other, so you can move through everything waiting on a decision without switching campaigns. Opening Review from inside a campaign takes you to the same console, filtered to that campaign, rather than a separate in-campaign review screen.
Rejecting can ask for a corrected take that carries your feedback into the new render, and the rejected video is kept as part of the approval record rather than deleted.
Review has three tabs. Queue is the per-creative decision described here. Requested reviews tracks every review you have sent outside Klyo: who holds each link, how many creatives they have got through, what they approved or sent back, and when the link expires, with revoke and resend on each row. Creative scores is the rubric readout across every creative that has been checked, the same advice read over a whole matrix instead of one clip at a time; see Reading scores across creatives.
Notes that point at a moment
Under the video, Feedback collects what everyone has said about this creative: each outside reviewer's verdict, and the notes anyone has left. Play to the moment something goes wrong and start typing, and the note is pinned to that timecode; clicking the timecode later jumps the player straight back to it. Write without playing and the note is about the creative as a whole. Your own notes can be removed again; everyone else's stay. Notes never decide anything, they just make sure "the logo is cut off" arrives with the frame attached.
Sending it outside Klyo
People without a Klyo login can still weigh in. Request a review in the Review console emails each person you name their own link, which opens the same finished videos with no sign-in. They take the videos in any order, approve one or send it back with a note, pin notes to a moment in the clip, and skip the ones they are not sure about. The arrows move between videos and View all lists every one, so a reviewer can change any decision they have not submitted yet. Submitting sends what they have decided so far and keeps their link working for the rest, so a long list can come back in several batches until everything is decided. A decision already submitted is locked on that link: a later visit shows it rather than offering it again. Each link lasts seven days, and you can revoke an outstanding one and send a fresh one.
What comes back is advice, not the decision. Several reviewers can disagree about the same creative and each verdict is recorded beside the others; the creative stays in review until you approve or reject it in the queue, which is the only way anything reaches the Activation Queue. Everyone on a review sees what the others have already flagged, so a second reviewer adds to the picture instead of repeating it.
The Creative Score at the gate
Beside that decision the console can show the creative's Creative Score: one pass over the rendered video read against a rubric, banded Excellent, Might improve, or Needs review. A badge in the header carries the number, and the panel under the Approve and Reject buttons breaks it into the rubric's four pillars, each signal marked detected, not detected, or not evaluated, with the cited moment clickable to jump the player there.
It is advice and never a gate: a low score does not block an approval or a push. A creative is checked automatically only when its campaign turned on Check every new creative; otherwise press Run check in the panel's header for the one creative in front of you.
What you can do today
- Expand a campaign into combination packages, repeatably and safely.
- Browse, filter (including Hide rendered), and page through combination packages across the Organization.
- Open a combination package to see its catalogue items, format, template, and campaign.
- Render or re-render a single cell from the Render Queue, a combination package's detail, or the campaign's own inventory, without a full campaign-wide render.
- Review every Final Video across all your campaigns from one console, approving, rejecting, or re-rendering one cell or in bulk. See Generation and render.
- Send in-review creatives to someone outside Klyo for a no-login decision, and let them answer in batches through the same link.
- Read a creative's Creative Score beside that decision, or request a check on the one creative in front of you.
- Switch to the Creative scores tab to read every checked creative at once.
- Rely on freeze-at-render keeping finished work stable.