After you hand a content output to Blogs, Email Campaigns, or Calendar, continue editing its publishable version in that workspace. Grow → Content keeps the original planning work and its connection to the destination.
Use reconciliation when someone has edited a linked record and you need Content's review status to reflect that work. For example, a teammate may revise a blog after its handoff, change an email subject, or update a social placement. Reconciliation helps you record and review those changes without creating another draft.
Start with the linked destination
Open the content item in Grow → Content, then select Activity & review. In Native state, find the destination and use its Open Blogs, Open Email Campaigns, Open Calendar, or other Open … link.
“Native” means the workspace holding the linked record. Check that record directly: its current copy, intended audience, media, links, schedule, and publication or sending status. For an email, include the subject and sender; for a social placement, include the platform and posting account.
The Content output remains a read-only snapshot after handoff. It may therefore differ from the copy you see in the destination. Edit the publishable version in its destination, and keep using the Content brief for coordination. Reconciliation does not copy the revised destination text back into the original draft or merge two versions of the copy.
If you have not created or linked a destination record yet, follow Scheduling and distributing approved content. There is nothing to reconcile until the item has a linked record.
Check what changed before using the button
Loading the item shows destination status and available dates in Native state. Read any warnings, then inspect Approval history and the item's activity. An older approval is not enough to establish that the destination's latest copy has been reviewed.
There is no separate reconciliation preview or side-by-side merge screen in this workflow. Reconcile / acknowledge native state acts immediately. It checks the item's linked records together, rather than only the record whose link you last opened.
Before selecting it, review all affected destinations, especially any already showing a change warning. If you still need edits, make and save them in the appropriate destination first. Do not use repeated clicks simply to clear warnings: the same button can also record your acknowledgement of reviewed changes.
If another person is editing the same output, agree which saved version you are reviewing. Save or preserve any unfinished Content edits before reloading the item or leaving the page.
Record a change, then acknowledge the reviewed version
- Open the item and select Activity & review → Native state.
- Open each affected destination and review its saved content. Resolve corrections there before continuing.
- Return to Content and select Reconcile / acknowledge native state once.
- Check the resulting warnings, output or variant review state, activity, and Approval history.
- If a newly detected change now needs acknowledgement, open the destination again and verify that the saved version is the one you reviewed. Once all affected records are ready, select Reconcile / acknowledge native state again and check the result.
When Cedros detects a new change to a linked record, it marks the connection as changed and invalidates the affected output or variant's previous approval. That work needs review again; the original brief and other channel outputs are not automatically rewritten.
A later reconciliation, with no further destination change, can acknowledge the reviewed version and record a current approval under your name. This is a review action, not just a refresh. The affected output or variant stays unresolved if it still has a changed, missing, or failed connection.
For example, after a blog's wording changes, one reconciliation can record the change and make the old approval stale. After checking that wording in Blogs, a later reconciliation can acknowledge it. If the wording changes again in between, Cedros detects another change instead of treating the earlier review as approval of the new version.
Not every status update is an editorial change. Scheduling an otherwise unchanged email, for example, can update its delivery status without making its content approval stale. Always read the actual result rather than expecting each reconciliation to create a new warning or approval.
For review assignments and separate brief, output, and account-variant approvals, see Reviewing and approving content.
Handle missing or unavailable records
A record is missing. Open its destination workspace and confirm whether it was deleted, moved out of your access, or replaced. Reconciliation does not recreate a deleted blog, email campaign, Calendar placement, link, or media asset. Ask the owner or administrator to resolve the connection before relying on its approval or creating a replacement.
A previously missing record is available again. Check its content before acknowledging it. Recovery can first mark the connection as changed so that the restored version gets a fresh review.
Calendar is unavailable. Retry after Calendar is accessible. A loading failure is not proof that the placement was deleted, and it is not a reason to create a duplicate placement.
A blog is archived or an email campaign is cancelled. Check whether that outcome was intended in the destination workspace. Reconciliation does not restore archived work, resume a campaign, or reverse cancellation. Handle any new delivery plan there.
The handoff failed or the result is unclear. Inspect the existing linked record before creating anything else. Keep the content item and its history while you resolve the issue; a connection warning is not a request to delete the planning work.
Resolve access and save errors
The reconciliation button requires permission to edit the content item and appears only when the item has linked records. Access to open or edit Blogs, Email Campaigns, Calendar, Links, or Media is separate. If you can see a warning but cannot inspect its destination, ask someone with the appropriate access to review it. See feature access.
If reconciliation reports an error, keep the message and check the item again before retrying. A failed response does not prove that no update was saved. Inspect the current warnings and approval history first, because another click may acknowledge a change that was already recorded.
If warnings remain, review each linked record. One healthy destination does not resolve a missing asset or a different changed output. Share the content item, affected destination, and exact error with your administrator if the problem persists.
Verify the review and delivery separately
Finish by checking that the relevant change warnings are resolved and Approval history shows the review you intended to record. Keep any corrections to the publishable copy in its destination workspace.
Reconciliation does not publish a blog, send an email, post to a social network, or cancel an upcoming delivery. It also does not verify every external platform on your behalf. Check the actual published page, campaign result, or social post and posting proof when confirming delivery.
If the item belongs to a larger campaign, return to the initiative and check its remaining channel requirements. Coordinating a multi-channel initiative explains how to assess readiness across the whole plan.