Scheduled tasks will fail in Qlik Sense, if the App contains Section Access while could be working fine from the script editor.
Investigating the log file <Servername>_System_Engine.txt shows a warning message similar to:
WARN domain System.Engine.Engine 89 6ac41964-2910-4a17-9162-c40119b2d3d6 domain\qliksense System: DetermineAccess: Failed to access the following document af18ffcb-6b60-4546-9fa5-f385172eebec with the user: 0 sa_scheduler 20181126T181325.903+0100 6864 7120 eaa1c5c2-1850-40cb-a490-0e6158df82b0 af18ffcb-6b60-4546-9fa5-f385172eebec 20181126T181055.000+0100 6ac41964-2910-4a17-9162-c40119b2d3d6
On the script log you will see:
Execution Failed
Execution finished.
Qlik Sense Enterprise on Windows governs access to resources (such as Apps) through the Repository Service. An account for each service is created in the PostgreSQL database during setup, such as the sa_scheduler account above. For the Scheduler to be able to access the App during reload, this account must be added into Section Access, not the account running the actual service.
See also the help documentation:
"The INTERNAL\SA_SCHEDULER account user is required to enable reload of the script in a Qlik Management Console task." Managing security with section access
Resolution:
Make sure the Qlik Sense internal (non-Windows) account INTERNAL\SA_SCHEDULER is added to Section Access with access ADMIN. See also Managing security with section access
Example
Section Access;
LOAD * INLINE [
ACCESS, USERID
ADMIN, INTERNAL\SA_SCHEDULER
];
