Opens in a new tab
Guide

Que and Templater: How They Work Together

Published November 13, 2026

A job travels through Que and Templater in one direction. It is created in a campaign, picked up by a satellite, merged into an Autograf by Templater and rendered to a file. Que keeps the record of each step and does not render anything itself. This article follows a single job through that trip, status by status, and shows where each handoff can go wrong.

It does not repeat the setup. If you still need the four components explained, or the steps for adding a satellite and creating a campaign, start with our explanation of what Que is and come back. If you are still deciding between the products, our comparison of Que and Templater covers that. We make both products, so this is the maker’s account. Every step below comes from our help documentation, our API documentation and answers from our founder. Where those sources are quiet, we say so and leave the gap open.

The satellite asks for work, and Que keeps the record

Our API documentation describes satellites as machines running an instance of After Effects that request data from Que through Templater. The satellite is the one asking. A Templater session with the Bot enabled goes to Que, finds jobs it is set up to process and works on them. As it does, the status of each job changes in Que and you can read the change in the Dash.

That makes the handoff an agreement between two systems. Que says which Autograf the job needs, which satellite should process it and what data goes in. The satellite has to hold the matching project. Our documentation says a satellite must have the job’s referenced Autograf installed, along with its dependencies such as fonts and effects, and that you must adopt your own workflow for deploying Autograf changes to each satellite. It suggests a sync folder service for that. Nothing in Que copies the project to your machines for you.

One job, from insert to finished file

To keep this concrete, take one job from a campaign. It is a JSON object of key-value pairs. Some keys are your data, such as a title or a tint color. Others are instructions: output names the file, target names the composition, and render settings and output module name the templates After Effects should use. This is a worked example built from the documented steps. It is not a customer story.

Stage one: the job is created

You can insert the job with the New Job dialog, with a batch import from a JSON, Excel, CSV or TSV file, or from your own application through the API. Whichever route you use, Que fills the gaps. According to the API documentation, if the job carries no aep value or no bot value, Que sets them to the campaign’s default Autograf and default satellite. If it carries no render-status, Que sets it to ready.

One job’s trip

A job moves through five stages

  1. Job createdQue sets missing values, Autograf, satellite, and render-status, to the campaign’s defaults.
  2. ReadyThe job has all its data and is prepared for processing but has not been queued.
  3. QueuedThe job is waiting in line for its assigned satellite.
  4. ProcessingTemplater is versioning and rendering the target composition with the job’s data right now.
  5. DoneThe render completed successfully and the satellite has written the output to its own disk.
Done is the render status; a separate stream status tracks deployment through Projector.

Values you supply win over those defaults. Our help page on inserting a job says that when you create a job from a JSON file, the property values in the file override any values derived from the campaign’s defaults. In the New Job dialog, the job status and satellite fields can force a status and a machine, and when no satellite is chosen the job goes to the campaign’s default. If a job lands somewhere you did not expect, read its Autograf and satellite values first.

Stage two: ready means eligible, not started

A ready job, in the words of our founder, has all its data and is prepared for processing but has not been queued. Nothing renders yet. The job waits until a Templater session picks it up, which is why the next stage is about the machine rather than about Que.

On the satellite, you press Enable Bot in the Templater panel. Our help page says that Templater then enters a server mode and begins checking your data source periodically at regular intervals. The button label changes to Disable Bot, and the Templater panel freezes except for that one button. The documentation lists this as the expected behavior, so a frozen panel on a Bot machine is not by itself a sign of trouble. The Enable Bot button belongs to the Templater Bot edition. Our API documentation puts the whole step in one line: assign jobs to an authorized satellite, then enable the Bot to begin processing jobs with a render status of ready.

Which jobs a session sees depends on its setup. You can link a campaign and filter jobs in Templater, and the Que Inspector shows the list a filter selects. We cover filters and paging in the Que explainer, and the Bot’s own settings in our guide to configuring the Bot.

Stage three: queued, processing, done

Our Que help page says jobs are typically processed from ready to queued to processing to done, unless they are canceled. Our founder’s definitions of each value are these. A queued job is waiting in line for its assigned satellite. A processing job is being versioned and rendered by Templater right now. A done job finished successfully. A canceled job was stopped before it finished. A failure during processing shows up as an error code, such as ERR::MEDIA for a problem with media assets or ERR::AFXHOST for an After Effects error.

The Bot documentation describes the same sequence for a data source with a render-status column. The Bot retrieves rows marked ready and updates them to queued. For each queued row it sets the status to processing, versions and outputs the target composition with that row’s data, and sets the status to done. If it meets an error, it writes a code such as ERR::MEDIA or ERR::AFXHOST instead. That page is written for the Bot with a spreadsheet source. We have no page that describes the same step-by-step writes for Que jobs, so treat the two as parallel descriptions and not as one document. Our guide to Que job states goes through each value and what to check when you see it.

Stage four: the file lands

When the render finishes, the satellite writes the output to its own disk. The Output Root is the directory where the satellite saves output, and it corresponds to the Destination field under Output Options in the Templater panel. The Footage Root is where the satellite retrieves footage from, and it corresponds to the Footage field under Batch Assets.

The naming scheme is one of three choices. With Unique, the satellite uses the job’s own ID as the file name. With Prepend, it uses the job ID as the name and treats the job’s output value as a folder path. With Override, it uses the job’s output value as both the name and the path. Our Bot documentation says that, because it is fully automated, the Bot overwrites existing files when two rows render to the same output file name. Under Override, two jobs with the same output value therefore point at the same file name. Choose Unique when you are not sure.

Stage five: done is not live

Our founder lists a second status for the same job, the stream status. It belongs to Projector and Que and describes deployment and distribution to a streaming or hosting platform. The first value he lists is pending, meaning waiting to be picked up for streaming or deployment. The last is onstream, meaning deployed and live. The full list is in our article on Projector stream status. For this trip, the point is that a done job and a deployed job are two different facts.

The satellite settings that steer the trip

The Que Dash shows a satellite’s profile when you expand it in the Satellites view. Several properties only describe the machine, such as its operating system, RAM, drive capacity and installed fonts and effects. A few decide which jobs the machine touches and what it produces.

Processing Scope says whether the satellite processes jobs from all campaigns or only from the single campaign linked to Templater. In Templater it corresponds to a checkbox in the Que Satellite Information group. A job waiting with nothing picking it up is a reason to read this setting.

Output Mode says what kind of assets the satellite outputs. Render outputs video files of target compositions in data-merged Autografs. Replicate outputs replicas of those compositions. Spot Check outputs still images or short video clips of selected frames. In Templater these are the checkboxes next to Actions in the Bot Settings group of Preferences. If a satellite has only Spot Check ticked, what it outputs is stills or short clips, which is not what a render job asks for.

Satellite output modes

Output Mode decides what a satellite produces

Output Mode What it outputs Templater setting
Render Video files of target compositions in data-merged Autografs Checkboxes next to Actions in Bot Settings group of Preferences
Replicate Replicas of those compositions Checkboxes next to Actions in Bot Settings group of Preferences
Spot Check Still images or short video clips of selected frames Checkboxes next to Actions in Bot Settings group of Preferences

Authoring App and Data App show the versions of After Effects and Templater on the machine, and Data Feed shows the URL the satellite retrieves job data from. When one machine behaves differently from another, comparing those fields is a sensible start.

Que does not offer load balancing. Que will not look at a ready queue and spread it across idle machines, so you assign satellites yourself. Our FAQ adds that you must verify that every required asset, font and plugin is available on any satellite you assign a job to. In the batch import dialog the choice is a single satellite dropdown for the file.

When the trip stalls, and what to check first

A job that does not finish has stopped at one of the handoffs above. Ask which handoff, and check that one. The questions below follow the order the job travels.

Was the job created with the right values? Open it in the campaign table and read its Autograf, its satellite and its status. A job that names a satellite other than the one you are running is assigned to a different machine. If that satellite was deleted, the job is unassigned and needs another authorized satellite before processing can continue.

Is the Bot enabled on the machine that was assigned? The Bot is a state of one Templater session on one machine. Our guide to adding and understanding satellites covers registration, and our troubleshooting article covers add and remove problems such as duplicate names, host names with odd characters, the plan’s satellite limit and expired security tokens.

Does the session’s filter include the job, and does the satellite’s Processing Scope reach its campaign? If you filtered to one campaign, a date range or a property value, a job outside the filter is outside that session’s list. Open the Que Inspector and read it.

Does the satellite have the project? The Autograf and its fonts and effects have to be installed on the machine, and our documentation says that is your workflow to set up. When a job ends in an error code, the code is the first clue: ERR::MEDIA points at media assets and ERR::AFXHOST at After Effects.

When a job stalls

Check these four things first

  • Open the job and read its Autograf, satellite, and status values
  • Confirm the Bot is enabled on the assigned machine
  • Check that the session’s filter and Processing Scope include the job’s campaign
  • Verify the Autograf and its fonts and effects are installed on the satellite
Follow the order the job travels, each question matches one handoff.

What happens when a satellite goes offline in the middle of a job? Our documentation does not describe a timeout, a retry or a reassignment, so we will not describe one. Last, test on a small campaign before you trust a status for monitoring. Create a few jobs, run them all the way to done, and open the output folder. That run shows which handoff in your own setup needs attention.

The bottom line is that Que and Templater are one pipeline with a clear seam. Que owns the data, the queue and the record of what happened to each job. Templater and the satellite own the project file and the render. Put the same Autograf and fonts on every machine, make each job name its Autograf and satellite or rely on defaults you chose on purpose, give each output a name that cannot collide, and read both statuses in the Dash. If you are still weighing whether you need Que at all, the Que page is where to start.

The questions below are worth settling when you plan a real batch. The answers come from the same documentation.

Frequently Asked Questions

Does Que send jobs to Templater, or does Templater fetch them?

Our API documentation describes satellites as machines running After Effects that request data from Que through Templater. You sign Templater into your Que account and authorize it, link a campaign, and enable the Bot. The Bot then works on jobs marked ready. Que stores the jobs and records their status.

What has to be installed on a satellite before a job can render?

The satellite needs After Effects and Templater, and it needs the job’s Autograf along with the fonts and effects that the project depends on. Our documentation says you must set up your own way to deploy Autograf changes to each satellite, and it suggests a sync folder service.

How does a job know which machine should render it?

Each job carries a bot value that records its satellite. When a job is created without one, Que assigns the campaign’s default satellite. You can choose a different satellite in the New Job dialog or in the batch import dialog. Que has no load balancing, so you decide the assignment yourself.

What happens to jobs when the satellite is deleted or offline?

If you delete a satellite, its jobs become unassigned and must be reassigned to another authorized satellite before processing can continue. If the satellite is simply offline, our documentation does not describe a timeout or a reassignment. If you rely on this, test it on a small campaign and see what your setup does.

What do the render status values mean?

Ready means the job has all its data and has not been queued. Queued means it is waiting for its assigned satellite. Processing means Templater is versioning and rendering it. Done means the render completed successfully. Canceled means it was stopped before finishing, and an error code such as ERR::MEDIA or ERR::AFXHOST means it failed during processing.

Is a done job already published to a video platform?

No. Done is the render status. Jobs also have a stream status, which belongs to deployment and distribution through Projector and Que, with values from pending to onstream. A video can be done and not yet live. Check both statuses when your workflow includes deployment.

Leave the first comment

Sign up

Stay up to date with Datclay's newsletter. We won't spam your inbox.

Newsletter Signup
Name
Name
First
Last

By submitting your email, you agree to our Terms and Privacy Policy. You can opt out at any time.