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.
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 content: 0 of 1 clips ready", "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.
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.
- Rely on freeze-at-render keeping finished work stable.