When a Queued Asset Does Not Produce
Telling a healthy backlog from an asset that has genuinely fallen out of the queue, and what to do about each.
Most reports of a stuck queue are not stuck queues. A production run takes one asset at a time, so a queue of twenty assets drains over days and an Overdue label is the normal look of a backlog.
There is one state that really does mean an asset will never be produced, and it is labelled separately: Not queued. Check that count first. If it is zero, nothing in your queue is being skipped, and the question is only about timing.
Everything here is read from Marketing → Content → Queued Assets.
Known Issues
An asset is marked Not queued, with a warning above the list
The asset sits at Approved rather than Scheduled. It keeps its date and looks scheduled on its plan screen, but only a scheduled asset is picked up for production. This happens when a topic is approved again after it had already been scheduled — the approval replaces the scheduled state.
Open the asset's reschedule control, confirm the date (the one already there is fine) and save. That returns it to the queue.
If several assets are affected, reschedule each one; the warning tells you how many there are, and clicking the Not queued count filters the list down to exactly those rows.
An asset has been Overdue for several days
The queue is deeper than the production runs since that date can work through. One asset is produced per run, and the run does not work strictly oldest-first, so a particular asset can wait while others around it are produced.
If the asset is not urgent, leave it — it will be produced. If it is, use Produce now on that row, which builds it immediately for the same price.
If the whole queue is consistently behind the dates you wanted, the schedule is more ambitious than the output you actually need. Reject what you no longer want, or reschedule the rest further out so the dates match reality.
"This asset has already been produced"
The asset was produced between the page loading and your click — most often by a scheduled production run reaching it first.
Nothing is wrong and nothing has been charged twice. Reload the screen; the asset will have left the queue. Find the finished piece under Produced Content.
"This asset is already being produced"
A build for this asset is already running, usually because the button was clicked twice.
Wait a few minutes and reload. One asset, one charge — the second request was refused precisely so it could not become a second charge.
"A scheduled production run is already in progress for this account"
A scheduled production run is building an asset right now. Because a run does not announce which asset it has picked, a manual request during one could end up duplicating the work it is already doing.
Wait a few minutes and try again. Scheduled runs produce one asset and finish, so the wait is short.
"This asset was rejected. Reschedule it before producing it"
The asset was rejected, so it has no date and is not in the queue. A stale browser tab can still be showing its row.
Reload the screen and the row will be gone. To bring the topic back, open its plan, approve the topic and schedule it again — everything Zyntro researched for it is still there.
"Production failed" after the wait
The build itself did not complete. The run is recorded, and a failed build does not leave a half-finished asset behind.
Try Produce now again. The asset is still queued and still has its brief.
If it fails a second time, the topic itself may be the problem — a brief with no keyword or no angle gives the build very little to work from. Open the topic from its plan and check that its brief is complete, or reject it and schedule a different topic.
The wait ended with "This is taking longer than expected"
The page stops watching after a while. That is the page giving up on watching, not the build giving up on producing.
Check Produced Content shortly afterwards; the finished draft usually appears there. Do not click Produce now again until you have looked — the asset may be complete, and a second request on an already-produced asset is refused anyway.
The screen says nothing is queued, but plans are showing topics
Those topics have no production date. A topic without a date is still a proposal, and this screen only lists dated assets.
Open the plan, tick the topics you want and use Approve & schedule. They appear here with dates immediately afterwards.
An asset I expected is missing from the queue
Either it belongs to another brand, or a filter is still applied, or it has already been produced or rejected.
Click Clear filters first — a state count can stay selected without being obvious. Then check you are in the right brand, since the queue only ever shows the brand you are working in. If it is neither, look under Produced Content: an asset that has been produced leaves the queue.
The offering column reads "Offering no longer available"
The offering the topic was researched from has been deleted or archived since the plan was built.
Nothing needs fixing. The asset's brief was captured when the plan was built, so it is still complete and still producible. If the offering is gone because you no longer sell it, the content is probably not worth producing — reject it.
Troubleshooting Guide
Does the Not queued count show anything other than zero?
Is the asset you are waiting for marked Overdue?
Do you need the asset before its date?
Frequently Asked Questions
No. Nothing is charged until an asset is actually produced. A queue can sit for weeks at no cost.
It makes the asset due, so it is produced by one of the next runs rather than on the spot. For a specific moment, use Produce now.
The asset leaves the queue, but the topic is not deleted. Open its plan, approve the topic and schedule it again. Everything researched for it — keyword, angle, audience, funnel stage and brief — is still attached.
A production run takes one asset per pass and does not work strictly oldest-first. Over a few runs the backlog clears, but a particular asset can be passed over more than once. Produce now is the way to force the order.
The charge is taken when the asset completes, not before it starts, so a build is not blocked by a low balance the way scheduling a whole plan is. Keep the balance covered for the queue you have committed to — if auto top-up is configured on your account, it is checked after each charge.
