🔍 Why this can happen
When a service is cancelled, posts that were already scheduled or queued may still be published. Cancellation may stop new activity without automatically removing content that was prepared before the cancellation took effect.
Posts can also come from another connected Search Atlas service, workspace, user, or third-party tool with access to the same social profile.
✅ What to check first
- Review the post’s publishing date and compare it with your cancellation date.
- Check whether the post was scheduled before cancellation.
- Review every Search Atlas project that can publish to the profile, including Social projects (All Projects, Pending Approvals, and Calendar View) and GBP Projects (Posts), plus every connected social profile.
- Check other tools or users that may have publishing access to the profile.
- Save examples of recent posts, including their URLs, dates, and publishing times.
🛑 How to prevent further posts
Remove or pause any remaining scheduled content in the platform, where available. You can also review the connected social profile’s authorized apps and remove access for services you no longer use.
If posts continue after scheduled content has been removed and access has been revoked, the source may be a different integration or account. Do not delete published posts until you have recorded their details, as this can make the source harder to investigate.
🧾 What to include in a support request
Provide the affected social profile, links to examples, publishing dates and times, your cancellation date, and the workspace or project involved. This helps the support team identify whether the posts came from queued content, another connection, or a different source.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.