Automation task runs more than 4 hours

[Riccardo]

I have a large app that requires a massive load script. This script runs for more than 4 hours.

According with the documentation, an Automation Task has a 4 hours limitation.

There is any way to extend this limitation, or a workaround?

[Shai_E · Accepted solution]

Hi @Riccardo ,

If it's a big app with a reload that takes more than 4 hours to complete you can change the "Do Reload" blocks run mode to "Start Reload And Continue" that way the apps reload will happen in the background and you wont have to wait for it to complete in the automation, the downside is that you won't get the normal output from the block that has the reload log.

[Riccardo]

Hello, thank you for you reply.

We need to reload the apps not in parallel but in serial way.

It all started with a reload that lasted more than 4 hours in total. To be able to break the reload into multiple reloads, we created multiple apps, but these must be executed in series by an automation. The automation with the 4 hour limit blocks the production process.

[hakana]

Hi,
You could use webhooks to make your automations/pipeline event-driven
The automation will start when the internal event is sent

You can use either:
- Automation run ended
- Reload finished / Reload Data Updated

[cotiso_hanganu]

My 50 cents:

Paralelizing some of the Qlik Sense Script processing might help cut the overall time, as well