Start controlled manual generation and follow every stage from topic selection to the final WordPress post.
When to use Create Articles
Use manual creation for the first end-to-end test, provider comparisons, troubleshooting, urgent approved topics and any change that should be verified before automation resumes.
Controls
| Control | Purpose |
|---|---|
| Article count | Number of eligible approved/queued topics to process; begin with one |
| Final status | Draft, Pending review or Publish for this manual batch |
| Start/Create | Creates background job records and dispatches workers |
| Cancel | Requests a safe stop after the current provider operation; preserves checkpoints and does not publish an incomplete post |
Eligibility before start
Publisher checks runtime licence access, global pause, topic state and available content policy. A topic in conflict, archived state or already owned by another generation job is not a valid duplicate start.
Live Pipeline stages
- Research: inventory/overlap, link candidates, optional SERP/GSC evidence and external-source validation.
- Writing: archetype, modules, brief, section plan and checkpointed section generation.
- Links: validation and insertion of real internal URLs and verified external sources.
- Images: featured and inline media plan, provider generation, WordPress attachment and alt text.
- Quality: report calculation, blockers/warnings and the configured final workflow.
What progress means
A moving progress indicator confirms that the job has reported a checkpoint; it does not prove that the final quality gate will pass. Open the completed report and WordPress post before treating the result as successful.
Recommended manual test
- Approve one specific, non-overlapping topic.
- Select one article and Draft.
- Start the job and watch each stage.
- Do not open competing jobs for the same topic.
- When complete, open the native post and article report.
- Verify author/taxonomy, links, media, quality and final status.
Cancel semantics
Cancellation is cooperative. Publisher allows the active API request to return, records the safest checkpoint and stops subsequent work. A draft or partial checkpoint can remain for diagnosis. Cancel does not delete the topic, job history, generated post or media automatically.
Retry and recovery
Retryable provider or worker failures are requeued with backoff. A running job with no progress for roughly 20 minutes can be recovered and requeued; an eligible queued job waiting more than roughly 3 minutes can be redispatched when status is checked. There is no manual Resume button in 3.7.6.
Failure handling
- Research failure: check provider access, optional integration state and source response; optional GSC/SERP absence alone should not stop the pipeline.
- Writing failure: inspect model access, quota, response limit and the last completed section checkpoint.
- Link warning: distinguish a safe shortage from an invalid/excess link blocker.
- Image failure: verify image provider separately; lower inline minimum only if the editorial policy truly permits text-only output.
- Quality failure: open the named blocker and article report; do not blindly retry unchanged inputs.
Completion checklist
- Job has a terminal state and no unexplained retry loop.
- Topic points to the correct generated post.
- Native post status equals the manual selection.
- Report contains research, structure, links, sources, media and quality evidence.
- History remains available for audit.
Related guides
Topic eligibility · Jobs and recovery · Reports
Manual jobs and schedule reservations in 3.7.6
A manual Create Articles job is independent of automation slot reservation unless it was explicitly created for that slot. Automatic publication uses only a quality-approved automation-ready article reserved to one future slot.