Recently I'm facing an issue (16/05/2025 onwards) while applying the bookmark in the backend using Engine API while the bookmark is created in the extension using Capability API in the frontend. We are authenticating the user with M2M impersonation, so we don't have issue on accessing the bookmark which was created by the same user in the front end even the bookmark is not published. but recently the user couldn't be able to access the bookmark until the App reload happens after bookmark is created. This also happening only at random time.
Note: When I publish the bookmark & tried it's working. After that even if I unpublish the bookmark it's still working.
Reason I thought: Having some issue on saving the bookmark while creating but after publishing it is saved & working. But the issue is happening randomly.
The issue of users being unable to access bookmarks until an app reload occurs, especially when it happens randomly, could be related to a few factors:
Publication and reload timing: When bookmarks are created before an app is published or reloaded, they may not be immediately accessible to all users. The reload process helps synchronize and update the app's data, including newly created bookmarks.
Access rights and permissions: If the bookmark was created by a user with different access rights than the one trying to access it, there might be permission issues until the next reload synchronizes these changes.
Dynamic data reduction: If section access is enabled in the app, it can affect bookmark accessibility. Reloading via the Hub might fail with an "Access was denied after reload" message, while reloading through the Qlik Management Console works but may lock out Hub users.
Changes in app ownership: If the app's owner has changed (e.g., due to the original owner leaving the company), it can cause issues with bookmarks and may require creating and setting a new default bookmark.
Caching and synchronization: There might be a delay in synchronizing bookmark information across the Qlik Sense environment, which a reload helps to resolve.
To mitigate this issue:
Ensure that app reloads are scheduled regularly to keep bookmarks and data in sync.
Check and verify user permissions and access rights for both the app and the bookmarks.
If using section access, review the script to ensure it's correctly configured.
In case of persistent issues, try creating a new bookmark, setting it as default, then removing it as default, and finally deleting it. This process can help reset bookmark-related issues in the app.
Thank you for your response on early. I have read all the points and had few doubts.
I don't think this issue is because of section access, because we are creating the bookmark inside the app using Extension (If I'm not understood properly, please explain this point). The second thing is if we already have any default bookmark in the application it will overwrite the previous one and even if I deleted the current it won't recover the old default bookmark.
What I think:
Instead of making it to default, I'm planning to publish it & unpublish after that if the app is not in personal/work space. As I already said in the question, I checked it manually & it worked. The problem in this might be I need to check whether the app is published or in shared space or not and then need to publish the bookmark. If the app is in personal or work space then I need to use app.doSave() while creating the bookmark, otherwise it will show "Access denied" error.
