Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Connect 2026 Agenda Now Available: Explore Sessions
cancel
Showing results for 
Search instead for 
Did you mean: 
cardonne_esrf
Contributor II
Contributor II

Task Reload Failure

I have an application published.

From the Qliksense hub, if I go to the stream "Published", open the app and manually reload it, it works fine.

When I created a (daily) reload task on the very same application, the task execution fails every time.

Does any one has an idea why or at least tell me how I can get more info in the reload task log file because "Execution Failed" is really not enough to understand why the reload fails!

Best regards.

Labels (1)
  • SaaS

1 Solution

Accepted Solutions
cardonne_esrf
Contributor II
Contributor II
Author

Hi All,

Thank you all for your answer.

The solution was to add 'INTERNAL\SA_SCHEDULER' as ADMIN in the script section access.

Cheers

View solution in original post

5 Replies
-SW-
Partner - Creator II
Partner - Creator II

This is typically due to security, either row level (Section Access) or connection level.

Can you check that your service user have the same permissions as yourself? Maybe start with the load after the resident table "BEHREXPENSE"

cardonne_esrf
Contributor II
Contributor II
Author

Thanks for the answer.

There is a section access in the load script.

So, does that means I have to add the Qliksense user, used for the reload tasks, in the section access?

Is it 'SA_SCHEDULER'?

-SW-
Partner - Creator II
Partner - Creator II

I assume you are using Qlik Sense on Windows.... go on the Qlik Sense Server and check the service user which runs the Qlik Sense services. 

surajmaraje_HSBC
Contributor III
Contributor III

Application is having section access implemented. Please add user which is used to run Qlik Sense services on servers. Add that user as ADMIN in section access. 

cardonne_esrf
Contributor II
Contributor II
Author

Hi All,

Thank you all for your answer.

The solution was to add 'INTERNAL\SA_SCHEDULER' as ADMIN in the script section access.

Cheers