Skip to main content Skip to complementary content

Known issues and limitations

This topic lists known issues and limitations in the current release. It isn't comprehensive, but it includes all significant issues identified so far.

General issues

  • SSO does not work when URLs do not match:

    • Users must use the same URL for Qlik Alerting that is configured for External Product Sign-On in Qlik Management Console (QMC).

      If Qlik Alerting is set up using a machine name or IP address in the API endpoint, users must use that same name or IP address to access the server. For example, if the URL in QMC is https://domainname:4552/api/users/authQXSession, users should access the Qlik Alerting server using https://domainname:4552, not https://localhost:4552.

  • Virtual proxy configuration requirements:

    • You may need to update the virtual proxy settings to support the new security approach used by the Qlik Alerting extension. Follow the instructions in Installing the Qlik Sense extension.

  • Unsupported special characters in virtual proxy prefixes:

    • Some special characters in virtual proxy prefixes are not supported in Qlik Sense. For example, d/e/v is not a valid prefix.

  • Alert sharing with users without app access:

    • If an alert linked to a Qlik Sense app is shared with a user who does not have access to the app, the accept link in the email results in an error. Although the alert is created, it will not trigger because the user cannot access the app.

Web UI issues

  • Mobile app does not support landscape mode:

    • Turning a mobile device horizontally does not switch the app to landscape mode.

  • Datetime field inconsistency across browsers:

    • Datetime fields may display differently due to default browser behavior.

  • Duplicated alerts do not appear until the list is refreshed:

    • In some browsers, the table is not automatically refreshed when an alert is duplicated. Refresh the browser manually to see the duplicated record, marked with "(copy)".

Qlik Alerting mobile app issues

  • Deep links may fail with special characters:

    • Deep links to Qlik Sense Mobile (QSM) or to a browser (when QSM is not installed) may not work correctly if special characters are used in a dimension name.

  • iPad Pro compatibility with deep links:

    • Deep links to Qlik Sense Mobile do not work correctly on iPad Pro devices running iOS.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!