Qlik Automation - too many requests

[rx98u5pq]

Hi all,

I have created a button in an app which triggers an automation to refresh an app.  (The automation runs fine, it is very simple and focusses on a single small ap).  The refresh of the app takes about 4 minutes.

However, it failed once and now seems to be "stuck" on the following message every time I try to trigger the automation:

"A pending reload request already exists for this app"

I logged in this morning and tried to refresh the app again and got this error.  there is no refresh occurring...so how do I kill any pending reload requests or is this a bug?

[janike548]

---

@rx98u5pq wrote:

Hi all,

I have created a button in an app which triggers an automation to refresh an app.  (The automation runs fine, it is very simple and focusses on a single small ap).  The refresh of the app takes about 4 minutes.

However, it failed once and now seems to be "stuck" on the following message every time I try to trigger the automation:

"A pending reload request already exists for this app"

I logged in this morning and tried to refresh the app again and got this error.  there is no refresh occurring...so how do I kill any pending reload requests or is this a bug?

---

The **"A pending reload request already exists for this app"** error indicates that the automation platform (likely Qlik Sense) has a **stuck or crashed reload job** that failed to properly clear its execution status, preventing any new reload from starting. To resolve this, you must access the **Management Console (QMC)** (in server environments) or the **Management Hub** (in cloud environments), locate the specific stuck reload task under **Execution History** or **Automation Runs**, and manually select the **"Abort"** or **"Cancel"** option to force the system to clear the erroneous status. If the status remains stuck on a server, a brief restart of the **Qlik Sense Scheduler Service** is the last resort.

[marksouzacosta]

Hi @rx98u5pq ,

Can you please send a screen shot of your application Reload History and your Qlik Automation Diagram/Canvas?

Regards,

Mark Costa

[rx98u5pq]

Hi Mark, thanks for the response:

it's a super simple automation:

 and the reload history is like follows:

What I have now found is that the refresh actually occurs even though it says the automation has failed.  So the trigger is correct but somehow the automation errors as it feels there are pending reloads.

[marksouzacosta]

I see you have a Do Reload inside a Loop block, that indicates the potential root of your problem.

If you have multiple items in your Loop Block and your Do Reload is pointing to a single App ID and your reload method is not 'Wait for reload to complete' then you will really have the error "A pending reload request already exists for this app". That means you are trying to reload the same application before it finishes its reload.

A very quick fix is to set the Do Reload to 'Wait for reload to complete' - if that is really the case:

However, this quick fix will make your application to reload X times - depending on the number of items in your Loop. What you should really do is to remove the Do Reload outside the Loop block - if possible.

Regards,

Mark Costa

[rx98u5pq]

Thanks Mark - I chose not to check "wait for reload to complete" as I was getting a 60s timeout error when refreshing.

Oddly, when I change the automation to below -  it fails after 1 or 2 minutes without explanation (the loop block at the bottom has been disabled).  it does not even attempt to reload the app.

[marksouzacosta]

Can you please select your Do Reload block and screen shot the properties? Like the image below:

[rx98u5pq]

So - to clarify.  with the loop the app refreshes (but the automation marks as failed)

Without the loop - the automation runs for longer and then fails without an error message.

[marksouzacosta · Accepted solution]

Ok, that explains everything.

With the Loop and with Do Reload set as "Start reload and continue" your Do Reload block is not holding the flow of your automation and it is trying to reload the application again while it still reloading - this is why the "A pending reload request already exists for this app" error.

Without the Loop block that won't be an issue. However, your Condition block will not be effective since will not check for the end status of the reload process. So, in your case you must set it to "Wait for reload to complete".

One other thing, try to remove the timeout of 2400 seconds and disable the Exit Loop block.

[janike548]

---

@rx98u5pq American Education Serviceswrote:

Hi all,

I have created a button in an app which triggers an automation to refresh an app.  (The automation runs fine, it is very simple and focusses on a single small ap).  The refresh of the app takes about 4 minutes.

However, it failed once and now seems to be "stuck" on the following message every time I try to trigger the automation:

"A pending reload request already exists for this app"

I logged in this morning and tried to refresh the app again and got this error.  there is no refresh occurring...so how do I kill any pending reload requests or is this a bug?

---

The "A pending reload request already exists for this app" error is caused by a stuck status where a previous app reload (likely in Qlik Sense) failed or timed out without properly clearing its "in progress" flag. To resolve this, you must access the Management Console (QMC) or Management Hub, navigate to the Execution History or Automation Runs for the app's reload task, and manually use the "Abort" or "Cancel" command on the stuck execution entry to force the system to clear the erroneous pending state and allow a new reload.