Review and manage Autopilot runs
Approve or reject articles waiting for review, retry or cancel a run, pause a schedule, and understand why Autopilot paused itself.
Before you start
An Autopilot schedule — see Set up Autopilot.
Steps
Step 1: See what is scheduled and what ran
On Autopilot, the table shows each project’s Status, Next run, Last run and Queue. Choose Calendar to see every run over time, and open a run to see its steps: generate article, generate featured image, publish to CMS, notify.
Step 2: Review an article waiting for you
When a schedule waits for review, open the run and read the draft. Choose Approve and publish to send it to the CMS as configured, or Reject — the draft stays in your articles and nothing is published.
Step 3: Retry or cancel a run
If a run stopped part-way, Retry remaining steps picks up where it left off; steps already paid for are skipped. Cancel run stops it; anything already generated is kept.
Step 4: Pause and resume
Choose Pause on the project to stop new runs; any run in progress will finish. Resume starts it again — missed runs are skipped and the next one is scheduled from now.
What you’ll see
You decide what reaches your site: approved runs publish, rejected ones stay as drafts, and a paused schedule writes nothing until you resume it.
Troubleshooting
“Paused — not enough credits”
A run could not afford its article. Add credits, then choose Resume.
“Paused — CMS connection needs attention”
The destination’s credentials stopped working. Choose Test on the project’s Integrations page, reconnect if needed, then Resume.
“Paused after repeated failures”
Several runs in a row failed. Failed articles are refunded automatically one hour after the failure. Check the latest run for the step that failed, fix the cause, then Resume.
“Paused — not included in your current plan”
Your plan no longer includes what this schedule does. Change the schedule (for example keep drafts in the app only) or compare plans on the pricing page.
A run started later than scheduled
If your workspace has committed a lot of credits to generation recently, a run waits until it can start rather than failing. It does not count as a failure.
Related guides
Set up Autopilot
Give a project a schedule and a queue of approved topics, and Autopilot writes, illustrates and — if you allow it — publishes an article on each run.
Publish an article to your CMS
Send the saved version of an article to a connected site as a draft, immediately, or at a scheduled time — and follow every attempt in the publishing history.
Credits and usage
How credits are held, charged and refunded, which credits are spent first, and where to see every charge on the Usage page.