Review the work before the status
Open the article and read the latest content, images, references and publishing details. Run Iris QA against that saved version. Inspect the findings rather than relying only on a score or green label.
Check whether claims are supported, product references are accurate, links are appropriate and the call to action matches the business goal.
Complete the workflow
- Save the final content and image choices.
- Run QA and wait for the result.
- Resolve required or critical findings.
- Complete approval with an authorised account.
- Select the configured destination and either publish or schedule.
- Review delivery status and open the resulting public URL.
An approval does not itself establish that a remote WordPress page or Nuvilo blog article exists. Publishing can still fail because of credentials, destination settings or a changed prerequisite.
Keep QA current
Editing after QA can invalidate its result. Treat a stale review as a prompt to check the updated work. The system’s readiness checks can prevent scheduling or delivery until the current version meets the applicable rules.
Autopilot has its own explicit approval policy and still blocks critical issues, missing or stale QA and other unmet requirements. Enabling automation does not turn every failed check into a pass.
If delivery fails
Read the recorded failure for the specific article and destination. Check the connection, website settings and permissions before retrying. If the outcome is uncertain, inspect the destination to establish whether content already exists.
For the Nuvilo blog, a published snapshot is separate from the editable draft. Later draft edits stay private until republished. For any destination, use the actual publication result and live link as evidence, then check the page as a visitor to confirm its visible content.