
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Error 403 when reloading published app.
My users get a 403 error message when they reload a published app using a reload button.
However: The script is executed, the new data is available. But still the error pops up.
I assume this happens when Qlik Sense tries to save the app, because after closing and reopening the app the previously loaded data is gone. It probably is a Security Rules issue.
I'm using this security rule:
(((resource.resourcetype="App" and resource.stream.HasPrivilege("read")
and resource.app.name = "Export Orders"
) or
(resource.resourcetype="App.Object" and resource.app.stream.HasPrivilege("read") and resource.objectType = "app_appscript"
and resource.app.name = "Export Orders")))
It has the privilege to "Update" which I assume is required to save the app, so the problem has to be somewhere with the resources.
Any help would be greatly appreciated.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The error appears to be a Qlik Cloud error.
If so, then it looks like the user(s) may not have role permissions in Qlik Cloud to perform the reload operation.
Qlik Sense rules do not migrate up to Qlik Cloud.
Please check out this recent community post regarding user management and roles topic.
Check the following to familiarize with App Reloading Access and limitations:
Space permissions and user entitlement
Kind regards...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm sorry for the misunderstanding. I'm using Qlik Sense Enterprise not Qlik Cloud.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok thanks...check out this article.
Also recheck this page as well:
Kind regards...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Kellerassel were you able to get this to work? I'm running into the exact same issue.
