Runs and the review queue
A run is one item going through a pipeline. This page covers trying a pipeline before you turn it on, reading what a run did, and answering what a pipeline asks you.
Trying a pipeline
On a pipeline's page, Try it runs the pipeline on a real item from its source. Choose one under On. If it says "Its sources have nothing to try it on yet", there is nothing to choose: a stream has to end, or a marker has to be placed, first.
| Button | What it does | Who |
|---|---|---|
| Dry run | Shows what each step would make of the item and what it would cost, without running anything or spending a credit | Editors and above |
| Preview for real | Runs it for real on that item, spending credits, but only ever leaves drafts | Admins |
| Run on this | Starts a normal run, for a pipeline that is on and whose source is Dropped in by a person | Editors and above |
A dry run gives each step's item count, cost and a sentence about what it would do, such as "Would write a short post about it with AI." The run's page gives the total. "What it costs could not be estimated" means one step could not say. A dry run stays in the list of Runs, marked Dry run.
Reading a run
Open a run from Runs on the pipeline's page. It shows the version it ran on, what was estimated and spent, and each step with the items that reached it. A run under way refreshes by itself.
| Run | Meaning |
|---|---|
| Starting | About to start |
| Running | Under way |
| Waiting | Waiting on a clip being cut, a person, a budget or a pause |
| Done | Finished |
| Partly done | Made some things and failed at others |
| Failed | Failed before reaching the outbox |
| Stopped | Somebody stopped it |
| Nothing to do | Every item was left out on the way, which is normal for a filter or a repeat check |
Under each step, each item has its own status:
| Step | Meaning |
|---|---|
| Waiting its turn | Not started |
| Running | Under way |
| In progress | Waiting on work it started, such as a clip being cut, or a batch closing |
| Held | Held while the pipeline is paused |
| Done | Finished. Anything it made is linked here |
| Left out | Left out, and it says why |
| Failed | Failed, and it says why |
| Stopped | The run was stopped |
When a step fails
A step that fails in a way worth retrying is tried again by itself, and shows how many tries it took. If it still fails, Try this step again runs it once more, for Editors and above. What it already made is not made twice.
Stopping a run
Stop this run ends a run under way: what has not started never will, and anything it was waiting on leaves the review queue. To stop everything a pipeline is doing, press Pause on its page. Runs under way then finish what they are doing, and nothing reaches out until you press Resume.
The review queue
The review queue, called Waiting for approval, is what the brand's pipelines are waiting on a person for. Open Pipelines and follow the count of what is waiting. Everybody on the brand can read it. Approving and rejecting take the right to publish the brand's posts, which is an Admin's by default.
Waiting shows what still needs an answer, and Decided shows what was answered.
There are two kinds of item:
- Let through? comes from an Ask a person step. Let through sends the item on to the next step.
- Post at a time comes from an outbox that proposes posts. Approve schedules it.
Each item names its pipeline and links to The run.
Approving a post
- Read the post. You can change its Title and Description here, and press Save changes before approving.
- Keep the time under Send at, or change it.
- Press Approve. The post is scheduled, as you.
If the time has passed, or no time was proposed, the post goes out at the next free time its timing allows, or straight away if there is none. See Timing.
To approve several, tick them, or use Choose all, and press the approve button, which says how many you chose. Each goes out at its proposed time. Each is decided on its own: one that cannot be, such as a post with no account chosen, says why, and the rest still go.
Rejecting
Add a reason under Why not (optional) if you want one, and press Reject. A post rejected is thrown away. An item rejected at Ask a person goes no further, and the run shows your reason.
You can also schedule a pipeline's post from Posts. The queue then has nothing left to ask about it.
From a phone
The queue works on a phone, and the page offers to tell you when something is waiting. See Phone.
If it goes wrong
See Pipeline problems.