Review, correct and approve posts

Prepare a post for review

Review starts with the content that will actually reach your audience: the default message, selected destinations, custom versions, ordered assets and provider-specific options. Check these before submitting. Your workspace needs an available approval workflow and the appropriate author and reviewer permissions. A queue may supply the default approval flow for posts assigned to it.

Open the post details to inspect its approval information and current state. An author and an assigned reviewer can see different worklist presentations of pending work. Use the workflow details and available actions to identify who needs to act, rather than treating every pending state as a publishing failure.

Submit and make a review decision

1. Complete the draft and inspect the content for every selected channel.
2. Submit it to the applicable approval flow. If the action is unavailable, check the post state, editing ownership and your permissions.
3. As an assigned reviewer, read the current version and its channel options. Approve when the configured requirements are satisfied.
4. Reject when changes are needed, and provide the required rejection reason. Make that reason specific enough for the author to correct the problem.

An approval request is not a successful publication receipt. Approved content must still meet scheduling, channel and provider checks before dispatch. When no approval flow applies, the remaining publishing checks still apply.

Use comments and correct the current version

Post details supports review comments and rejection history. Where a comment is associated with a passage, explain the requested change in that context. Resolve a comment after addressing it; resolved comments remain part of the review record. A resolved comment does not independently approve the post.

Editing content that has entered review or scheduling can pause its publication and cancel or restart the approval process. This protects against sending a version that differs from the one reviewed. After editing, inspect the new state and use the available reschedule or submission action. Do not assume that saving revised text preserves the previous approval or publication time.

Use Auto Reviewer for rejected text

Auto Reviewer is an optional post setting for automatic correction after rejection. When enabled and its prerequisites remain valid, the Posts Agent uses the rejection reason to correct the base text and resubmit the post into the approval workflow. The visible progress can include correction queued, correcting with Agent, applying correction, and corrected and resubmitted.

This is not an independent authority to approve content. Resubmission returns the correction to the existing workflow. The implementation applies a new base-text revision; it does not promise to repair every custom channel version, attachment, target choice or media setting. Review those separately, particularly when the rejection concerns a destination-specific requirement.

Resolve a stalled review safely

If automatic correction fails, inspect its reported state and the rejection history before editing manually. The author must remain active and authorized, the rejection and draft revision must still match, and the configured Agent and workflow must be available. A later edit or permission change can invalidate an in-progress correction. Automatic retries are bounded; repeated failures are not a reason to remove the approval requirement.

If an approval action is missing, confirm assignment and role with your administrator. If the time has passed or a post is paused for editing, choose a valid future schedule and complete the necessary review again. Inspect the final channel receipts after publication. See troubleshooting for the difference between pending review, a blocked schedule and an uncertain delivery.