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

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Announcements
Talend Cloud AWS EU Scheduled Outage: Starting Tues 26 May 21:00 CEST with expected completion Wed 27 May 01:00 CEST
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
luke_brady
Contributor III
Contributor III
‎2026-03-12 06:15 AM

Scheduled reload with direct access gateway abandoned (logs inside)

Hello,

we have recently had a lot of complaints regarding jobs failing with the following error


(Requested endpoint could not be provisioned due to failure to acquire a load slot: Command getReloadSlot error for reload ..."

 

It's recommended to update the gateway to the latest version here: https://community.qlik.com/t5/Official-Support-Articles/Requested-endpoint-could-not-be-provisioned-...

However we are already using the latest version and I already configured the gateway to request slots and load data asynchronously with the following:

OPTIONAL_CAPABILITIES=AsyncLoadSlotRequest,AsyncLoadDataRequest

 

I have checked the connector-agent logs and found the reload ID to see what exactly the problem is and have found the following:

2026-03-12 07:37:17,099 [ 96] [INFO ] DAG - RequestId=NA ClientSessionId= ReloadId=... AppId= Message=DataPipeInitializationInfo size: 359 bytes
2026-03-12 07:37:17,100 [ 96] [INFO ] DAG - RequestId=NA ClientSessionId= ReloadId=... AppId= Message=agent-session-info: DataKeyInfo size: 135 bytes
2026-03-12 07:37:17,377 [ 66] [ERROR] DAG - RequestId=NA ClientSessionId= ReloadId=...  AppId= Message=Calling stream/command complete for ...: Response=Gone, Attempt: 1 of 10



2026-03-12 07:39:16,900 [ 16] [INFO ] DAG - RequestId=NA ClientSessionId= ReloadId=... AppId= Message=agent-session-abandoned: Load request never received for reload ..., abandoning session
2026-03-12 07:39:16,901 [ 16] [INFO ] DAG - RequestId=NA ClientSessionId= ReloadId=NA AppId=NA Message=Releasing processes for Id (ReloadId/ClientSessionId): ... . 0 potential process(es) found.
2026-03-12 07:39:16,901 [ 16] [INFO ] DAG - RequestId=NA ClientSessionId= ReloadId=... AppId= Message=agent-session-close: Close session due to expiration - Web socket with state of Open and ReloadEventState of None closing...
2026-03-12 07:39:16,901 [ 96] [INFO ] DAG - RequestId=NA ClientSessionId= ReloadId=... AppId= Message=Writing ledger file to C:\Program Files\Qlik\ConnectorAgent\data\logs\reloads\2026-03-12\....json

 

I've removed the reload ID above, but it seems that a request was never sent for a load slot in the first place? There is also a 2 minute gap between the beginning of the attempt to load and the session being abandoned.

Can anyone explain this or know what the issue is? This is happening semi-frequently and colleagues are beginning to question the reliability of Qlik Sense SaaS as a product. 

Are there some configuration settings that I'm missing or can anyone advise me on how I could look into this further?

 

Thanks.

164 Views
0 Replies