Download Script Log Not available on Failed Tasks

[mikelutomski]

We are running Qlik Sense April 2019 Patch 1, 13.21.2, on a multi-node system (5 nodes).  

The issue we are having is the 'Download Script Log' button on Failed scheduled tasks is not functional.  It works for tasks that run successfully, but not for the failed or error results.

Our tasks are for our Published apps only, and our Load Balancing rules force those scheduled tasks to run on our Engine or Central nodes

We are able to locate the logs based on the Task status informational popup window.  It shows me which Node the task ran on.  We go to our Archived Log folder, select that Node, and open the Script folder.  ArchivedLogs-->Engine Node-->Script

We have already attempted to stop & restart services on that Node, which was unsuccessful.  We then did a full restart of the environment, which was unsuccessful as well.

The QMC is showing all nodes as synced.

Has anybody else experienced this issue or come up with a solution?

Thank you in advance.

[Anil_Babu_Samineni]

We have different error identifier type.

1) Error -- There could be log file not found since It failed in the node somewhere. To identify issue, we did 3 business days work shop using Script Audit error from "Operations Tools"

2) Failed -- We will get log file with information

3) Success etc.

[Anonymous]

The button will only be select-able if a script was created. The process did not get that far.  More clues may be found as to what is wrong if run from the HUB data load editor. 

[Anil_Babu_Samineni]

@Anonymous 

We got many times even in Hub it runs without error.

Findings:

1) If there are many in the Queue, This will come as Error not failed

2) If any proxy or node is not synchronized properly we will not find anything

3) If any service failed during Load balancing it throws error

[Anonymous]

In that case please review this article https://support.qlik.com/articles/000008047 as you may need to make adjustments as to the number of reloads that can be handed by your available resources. The time to wait may also be extended. 

If everything is set well and there remain failures, note the time and check the *_system_engine log at this location at the time of failure: C:\ProgramData\Qlik\Sense\Log\Engine\Trace 

There should be a clue to possibly what occurred. 

The *_system_scheduler log located here  C:\ProgramData\Qlik\Sense\Log\Scheduler\Trace is useful in watching what is happening during the task run and will also provide clues as to what happened. 

EDL

[Anil_Babu_Samineni]

This is what we've done already. But, extending concurrent reloads is not the permanent solution since there are many reloads (~50 apps) running on that time. So that, Sudden't it is changed to Slave mode since there are many in the queue. 

Solution, resolved using "Change the schedule" time for few apps and using load balancing on the same.

And, About logs really not helping for my case. Off course, foe others may helps. Thanks for that !!