Configure deliberately
Autopilot coordinates supported planning, generation, QA, approval and scheduling stages for the selected website. Its behaviour depends on the stages you enable, product access, package limits and the current content state.
Start with a small plan. Review the settings and decide which stages should remain manual. A saved setting authorises only the supported workflow described by that control.
Read the progress correctly
The banner distinguishes preparation from publication. Preparation opens is the earliest planned start for applicable work. Publication planned is the saved time when approved content is intended to go live.
Queued means the work is waiting for a worker. Running means the workflow has started. A recorded percentage is progress from that workflow; an indeterminate indicator means there is no reliable percentage yet.
Follow the dependency
- Open the linked article or post when the banner needs attention.
- Read the exact blocker.
- Complete the required brief, content, QA or manual approval step.
- Repair missing permissions, credits or connections if those are the cause.
- Use the offered retry or resume action when the work is ready.
Quill articles and independent social posts are prepared within their supported preparation window. A supporting social post also depends on its source article reaching a suitable saved stage. Planning a date far ahead does not immediately generate everything.
Keep approval meaningful
For Quill automatic approval, current Iris QA and the applicable SEO/check thresholds still matter. Critical issues, incomplete checks and stale results can block scheduling. Inspect any tolerated findings and the suggested fixes.
A temporary disconnected browser does not stop all background work. Refresh the recorded status before retrying. If the source changes, dependent work may need review again. Autopilot does not remove the need to confirm final delivery and inspect the public result.