Turning automation on
Open Publishing in the Content SEO section of the sidebar and select the correct project. Draft for me enables scheduled generation with approval-required publishing. Full autopilot enables scheduled generation and automatic publishing. Manual selects manual publishing and turns scheduled generation off. The settings screen requires a destination before enabling either automated preset. The underlying generation selection rules also depend on publishing mode and the publishing setup, so the presence of a connection is not a complete eligibility check. After a change, verify the resulting settings, especially if saving reports an error. The preset uses separate saves, and changing it is not a cancellation action for all queued work. See Publishing Modes & Autopilot.What runs automatically
The current generation scan selects ideas that:- are To be generated (
to_be_generated); - have a scheduled date matching the server’s current day;
- have completed topic planning;
- belong to a project with auto-generation enabled;
- are not already claimed by another operation;
- meet the applicable publishing-setup and access conditions.
Per-run safety caps
The current scanner limits candidates per scan and limits selected work from an individual project. It also staggers dispatch. These controls bound a scan’s work; they do not certify content quality or guarantee that every eligible project receives an equal turn. If several posts remain pending, inspect their dates and statuses rather than assuming they will all finish in the next run. Selection order, queue availability, eligibility, and the scan window can affect which work proceeds.Quota safety net
The worker checks the project’s applicable generation allowance and access before writing. Generation usage and planning headroom are separate counters; see Quota & Limits. For a quota-exhausted idea, the current worker can defer it into a later cycle where its deferral conditions permit. Other quota or access failures can block the attempt instead. A reset alone does not promise resumed generation: access, auto-generation settings, completed planning, and the future date still matter. Do not interpret these checks as a billing guarantee or a promise that every failure returns an allowance. Read the specific status and error for the affected idea.Missed posts
The normal automatic scan selects the current server day, rather than generating every past-dated idea. A separate sweep can move unclaimed, past-dated To be generated ideas to Missed, shown as Schedule Missed in the detail view. A missed idea needs your attention. Open it, review whether the topic still matters, and use its available manual generation action if you want the article written. Changing its date alone does not change a Missed status back to To be generated. See Time-Based Scheduling & Missed Posts. The sweep is bounded, so a past date does not establish that every overdue idea has already been marked Missed. Check its actual state.The auto-publish path
In automatic publishing mode, a successful generation can schedule a later publishing attempt. The handoff includes a randomized delay and a separate publishing scan. That is queue behavior, not a promised time from writing to a live page. Check both outcomes:- Did generation produce the intended draft and images?
- Did publishing deliver the intended version to the actual destination?
Why generation is paced
Staggering dispatch helps spread requests across the queue instead of launching all selected jobs together. It does not establish that a slower job is more accurate or that busy periods cannot fail. When diagnosing a delay, distinguish a pending idea from an active generation and a generated draft waiting to publish. Clicking generation repeatedly can conflict with work already in progress; inspect the existing job before requesting another one.What you’ll see in the dashboard
Use the calendar and blog detail page to inspect the current status. Generating means writing is underway. Pending Review, Scheduled, Published, Generation Failed, and Publish Failed describe different later outcomes. Read the accompanying error or action rather than treating all non-published statuses as the same delay. Refresh or reopen the page if its information appears stale. A progress message or internal SEO score is not an accuracy certificate, and Published should be checked against the actual website. See Blog Status Lifecycle for the state names.A note for regulated businesses
A configured compliance profile can place holds or block publication. Its findings do not replace the appropriate professional review, and absence of a warning does not prove that such a review happened. If a reviewer must decide on factual, legal, medical, or other specialist claims, use a review-first workflow and assign that responsibility explicitly. Check Compliance Profiles for configured publishing behavior rather than treating autopilot as professional approval.Related
- Publishing Modes & Autopilot: select and verify the controls.
- Quota & Limits: interpret generation access and counters.
- Time-Based Scheduling & Missed Posts: inspect dates and recover relevant missed ideas.
- Publishing Errors & Retries: investigate delivery after generation.
