Personal Bookmarks require browser refresh to work or be created

Hi saul009​,

Thank you for reaching out to Microsoft Fabric Community.

This looks like a power bi service issue with the report session when switching between reports in the same App. The personal bookmarks are still present, but they may not respond until the report session is refreshed.

As a workaround, please use the Refresh option in power bi or refresh the browser after switching between reports in the App. Since the bookmarks work again after refresh and the issue occurs across multiple browsers, this does not appear to be an issue with the saved bookmarks themselves.

Thanks and regards,
Anjan Kumar Chippa

Hi saul009​,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I provided for the issue worked? or let us know if you need any further assistance.

Thanks and regards,
Anjan Kumar Chippa

Hi v-achippa,

Unfortunately the workaround is not the solution to the real issue here, which is the one we are trying to solve. But I appreciate your attention to this matter.

Both symptoms you describe point to the same root cause a stale client-side session/report-instance reference that doesn't get refreshed when you navigate between reports within the same App shell (as opposed to fully reloading the page). This matches prior confirmed bugs where the report iframe/session token became stale during in-app navigation without a full page reload, and a hard refresh forced a new session to be established.

Issue 1 (can't create): the client is likely trying to write the bookmark against a session reference that's no longer valid for the newly-loaded report, since App navigation doesn't force a full browser reload.

Issue 2 (existing bookmark does nothing): clicking silently fails rather than erroring because the bookmark apply call is firing against that same stale session context, consistent with your point that it isn't corruption, since it works instantly after refresh with no recreation needed.

What I'd do in your position:

File it via the in-app "Give feedback" Issues page with your exact repro steps. This is a support. fabric or app.powerbi.com "Help > Report a problem" submission. Since you have multiple users, both Premium and Fabric environments, and multiple browsers reproduced, this is a strong, well-isolated repro that's worth Microsoft's Product team actually seeing rather than just community forum visibility.

Open a formal support ticket if you have Premium/Fabric capacity — this gets you an actual case number and engineering escalation rather than community troubleshooting, and two-week-old regressions affecting multiple users are exactly what support tickets are for.

Workaround to reduce (not eliminate) the friction: encourage navigating to reports directly from the Workspace/App list (fresh URL load) rather than via in-app left-nav clicks between reports, since a few older similar threads noted the issue didn't reproduce when a report was opened fresh from its own URL rather than via in-app navigation. Worth testing whether that holds for you too, as a partial workaround while it's open with support.

Capture browser console errors (F12 → Console/Network) at the moment a bookmark click does nothing. Since there's no visible error to the user, there's a good chance the network tab shows a failed/400 call when you click the bookmark, and that detail will make your support ticket far more actionable.