In this article, we will go through possible ways to recognize out-of-memory errors that can happen within automation, the root cause, and best practices to avoid/get rid of memory issues.
Out of memory errors can be identified if any of the below occurs
Download job history by clicking the 'Export this run' button and check if memory usage accumulative sum exceeds the above limit.
Export-Job-Run
The automation runs out of memory if it has the following blocks with huge data or dealing with larger lists
Let's walk through different ways of resolving memory issues by recreating the automation / changing the behaviour of automation
automation may fail with an out of memory
error for very large lists. So in order to make the deletion process work we can change the behaviour of the automation. Instead of deleting records based on the comparison, we will implement automation in any other possible ways described below
On deletewebhook event from the source platform, to delete records in the destination. Please get in touch with our support team if a connector is missing webhooks (that should be available according to the API documentation). Refer: https://help.qlik.com/en-US/blendr/Content/design-patterns/design-patterns-to-delete-records.htm
My cause to this issue is trying to send multiple pdf-reports. Trying to move customers from on prem installations with Nprinting to Saas is not easy. I hit this limit at around 60 reports and the only way around it I found is using copies of the same automation and using the call automation block in combination with a distinct field value or variable to separate the reports in the different automations. Not a practical solutions when I need to send out 300-500 different versions of the same report. How would you go about doing this? We need a better option if we're going to be able to move Nprinting customers to Saas.
Hi @_Anders_
Could you please share the automation json file which failed for you?
What error did you get?
Is it an Execution has failed error?
Thanks
Yea, please have a look @AfeefaTk . I put the automation in a dropbox. I have a log as well but I don't want to share this openly since it contains e-mail addresses and names.
I create a two side pdf report and use get straight table data in two loops, first selecting a person and then going through all customers connected to this person generating a report for every customer, before going to the next person. I usually get out of memory around report 60, so I tried splitting this into two automations but it does not seem practical since I now hit the ceiling again and need to split it into three automations. And I now face a similar task but with more than 300 reports need to be sent.
Hi @_Anders_
Is it possible for you to share the automation json file and also the job run id?
Thanks
@AfeefaTk So I did som tests and it seems it's the send mail box that takes up most memory capacity. Running the reports and saving them to OneDrive I could do without problem for 120 reports, but instead of saving them sending them by mail only got me to report 58 before the job ran out of memory.
Automation id that failed is cc218dc0-ce26-11ed-ac38-27f606065a5b and the run id 45542550-ce27-11ed-82a5-d505a652cb1f.
Hi @_Anders_
We are investigating this issue.
Please allow us some time and we will get back to you as soon as we have an update.
Meanwhile could you please let us know if you have already opened a salesforce case?
If yes, could you please share the salesforce case number?
Thanks
@AfeefaTk I have made no other report on this issue.
I can confirm that a fix released today solved this issue. At least for up to 120 reports sent by mail in one automation witch is the most I tired so far.
Hello @AfeefaTk ,
I have the same problem with the bloxk export app.
I try to backup all applications in shared space, the ticket number is 00094666: Automation failed without error
Can you help me ?
Thanks,
Paul
Hello @paulcalvet
Your ticket is being actively worked on and our support engineers will be assisting you in accordance with our SLAs. We will collaborate internally to get the expertise we need.
All the best,
Sonja