If a Changelog post isn't behaving the way you expect, find the scenario below that matches what you're seeing. Most issues come down to placement, segmentation, or scheduling.
A published post isn't showing up
Work through these in order:
Placement. Confirm the post is set to appear where you're looking — the widget, the standalone page, or both — in the post's Changelog options.
Segment and URL filters. If the post is segmented or restricted by URL, only matching visitors will see it. Make sure the visitor matches the segment.
Draft vs. published. Confirm the post is actually published, and not still a draft or scheduled for a future date.
If it's specifically the standalone page where the post is missing, see Why is my post not appearing on the standalone page?
A post won't save, publish, or edit at all
If you can't create, edit, publish, or delete a post, check two things first:
Your role's permissions. Post actions (create, edit, publish, delete, archive) are controlled per-role in Settings > Team. If your role doesn't have the relevant permission enabled, the action will be blocked even if you can see the Changelog editor. Ask an admin to check or update your role's permissions.
Whether the Changelog is enabled at all. Go to Settings > Widget > Buttons & Triggers and check the Changelog section. There are two separate switches there — “Enable Changelog on the widget” and “Enable Changelog on the standalone page” — so make sure the one for where you're looking is turned on. Posts won't publish or display in that location until its switch is back on.
Still stuck? Contact our support team.
A scheduled post didn't go out at the set time
Confirm the publication date and time, and double-check your timezone.
Make sure no expiration date has already passed.
For how scheduling and expiration work, see Scheduling a post (including expiration).
Keep in mind that scheduling and expiration are whole-post settings — they can't be applied to just one placement (e.g. a Topbar) while leaving others active. If you need a boosted announcement to expire separately from the main post, create it as its own post.
Editing a post didn't notify users again
This is expected. Editing a published post is silent — users who have already seen it won't be re-notified. If you want to re-announce an update, publish it as a new post. See What happens if I edit/republish a post?
A popup is showing that shouldn't be
Check your active posts and the segments assigned to them.
Review any force-display or auto-open settings that might be surfacing the post.
A permalink opens the standalone page or a different post
This is usually expected behavior, not a bug. If a post is segmented and the visitor doesn't match the segment, the permalink routes them to the standalone page instead of the post. Confirm the visitor matches the post's segment. Learn more about segmentation.
Still stuck after these checks? Contact our support team with the post and a description of what you're seeing, and we'll help you track it down.