Qlik Troubleshooting

This page lists common errors when connecting Sifflet to Qlik, and how to fix them.

Permissions

No Qlik Spaces Found

Symptom: Test Connection fails with:

No Qlik spaces found

Cause: the OAuth client can't list any space, usually because it doesn't have the admin.spaces:read scope.

Fix:

1. Check that the OAuth client has all the scopes listed in step 1.
2. Click Test Connection again.

No Qlik Apps Found

Symptom: Test Connection fails with:

No Qlik apps found

Cause: the selected spaces don't contain any app, or the OAuth client can't list apps, usually because it doesn't have the admin.apps:read scope.

Fix:

1. Check that at least one selected space contains an app.
2. Check that the OAuth client has all the scopes listed in step 1.
3. Click Test Connection again.

No Qlik Connections Found

Symptom: Test Connection fails with:

No Qlik connections found

Cause: the OAuth client can't list any data connection, because it doesn't have the user_default scope, or isn't a member of the spaces that contain data connections.

Fix:

1. Check that the OAuth client has the user_default scope.
2. Add the OAuth client as a member with the Can consume data permission to every space that contains data connections, as described in step 1.
3. Click Test Connection again.

Lineage

No Access to the Qlik Lineage API

Symptom: Test Connection fails with:

No access to the Qlik lineage API

Cause: the OAuth client can't read the lineage of the apps of the selected spaces.

Fix:

1. Check that the OAuth client has all the scopes listed in step 1, and is a member of the spaces that contain the apps' data connections.
2. Click Test Connection again. If the error persists, contact Sifflet support.