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, scheduling, or a change someone on your team made — and the post's own history will tell you about that last one.
First: check the post's history
Every Changelog post keeps a version history. If a post's status changed and you don't know why — it went back to draft, or it went live earlier than you planned — open the post and look at the History panel on the right-hand side. It lists each saved version, with the date and time, the teammate who saved it, and the status the post was in at that point. The current version sits at the top.
Because each save is recorded, the history also shows when the post's content was edited and by whom, not only when its status changed.
Check this before assuming the post changed on its own. Most of the time it's a teammate action, and the history tells you who and when in one look.
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?
If the widget opens but the feed inside it is completely empty rather than missing one post, that's a different problem — see The widget opens but the feed is empty in Troubleshooting: the Beamer widget isn't appearing on my site.
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.
Whether the page itself has stopped working. If buttons and menus on the Changelog page do nothing at all, and the browser console is showing errors, this is not a permissions problem. See below.
Buttons on the Changelog page do nothing
If the Create post button, and other controls on the Changelog page, do nothing when clicked, and the problem follows you across browsers and persists for an account with full admin rights, the cause is usually a duplicate element ID in the content of one of your posts.
This happens when content is copy-pasted from one post into another. The paste can carry an invisible container ID along with the text. Two posts then share an ID, which breaks the script that runs the Changelog page, and controls stop responding.
What to do:
Think about what was pasted recently. A sign-off, a footer, or a standard block copied from an older post is the usual source.
Contact our support team. We can find the duplicate ID and strip it from the post content, which restores the page. Tell us roughly when it started and which posts were edited around then, and include a Jam recording if you can. Jam captures the console, which is what points at this.
To avoid it recurring, retype or paste-as-plain-text when reusing wording between posts, rather than copying formatted content across.
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.
The same link works sometimes and not others
If a link to a post works on one page of your app and sends people to the feed root on another, the segment your site is sending Beamer is probably changing between those pages.
Sites often pass a different segment per screen. If the post is assigned to one of those segments and not the other, a visitor who clicks the link from the wrong screen arrives carrying a segment that cannot see the post, and Beamer sends them to the feed. The link is correct. The visitor's segment at that moment is not.
This is also what happens when your site sends a segment value that does not exist in your Beamer account. An unrecognised segment matches nothing, so the visitor can see no posts at all.
To check:
Compare the segment your site sends on each page. Look at the filter value in your
beamer_configon the page where the link works and on the page where it does not.Confirm every segment your site sends exists in Beamer. A value your site passes that you have never created in Beamer will match nothing.
Either narrow what your site sends, or widen what the post is assigned to. Stop sending the segment that has no access on that page, or create it in Beamer and assign the relevant posts to it.
Opening the same link with the working segment appended as a URL parameter is a quick way to confirm this is the cause before changing anything.
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.