We have Nprinting reports, Generate connection cache shows the status as completed, but it wont publish the report and again it will start generate connection cache automatically.
Qlik NPrinting September 2018 SR2 - Version: 22.214.171.124
Qlik Sense November 2018 patch 3 - qliksense server 12.44.5
I came back to this topic because i think there is a bug in NPrinting.
I observed similar behaviour on one of the tasks I am executing via API. I am sending single POST method, but then task gets triggered multiple times.
I am not sure if this is something on NPrinting side or maybe (in my case) Qlik Sense REST connector... If the issue persist then I will log a support case re this.
You may want to do the same as it will be easier to troubleshoot or replicate once we have data from multiple environmnets.
I am gathering logs now to see if there is anything in them
@Lech_Miszkiewicz - Thanks for the below update. We will also gather the logs and will log a case with Qlik .
Kindly requesting you to keep us posted if you come across any alternate solution to this.
Purely from NPrinting point of view and Qlik Sense load script we are using I don't see anything what would trigger reload multiple times.
I am assuming it has something to do with actual RESTFull API call over REST connector which I am not an expert in and dont know how to debug.
You may want to turn on DEBUG mode on REST, NPrinting and Qlik Sense logs to gather as much data as it is required for possible support case. Check help site on how to do this!
Answering those questions would possibly allow us to narrow it down to one of the components...
In my case this is new and started recently when I upgraded to Qlik Sense February 2020
Please link this conversation in the support ticket. At the moment I'm not aware of a similar bug so I think it is better to investigate.
Hi @Ruggero_Piccoli ,
sure I will.
it will be hard one to investigate as issue is hard to replicateand and does not always happen. For me it just started few days ago - I didn't even noticed it until one of the users asked me why we are sending the same report 2,3 sometimes more times minute after minute...When I sterted looking at report generation history i noticed that it started happening since we did upgrade..
unfortunatelly I cannot now link it to either Qlik Sense or NPrinting upgrade as both were done in very close time.
anyways - I will keep you posted.
I am going to observe this closely now and will log ticket once I am confident that there is nothing wrong with the way i set it up.
Can it be QS that does some sort of profiling of the data and/or check's the data connections?
I've had issues recently with a project Im working on where i create app+connection+report in the QS script. If i duplicate this app (the script uses the documentName() as app id for the created NP connection) and press the Data button (instead of menu - data load editor) i can see that my post calls are sent to NP. This should be a "as standard the user would like to go to Data Manager instead of data load editor" issue but i just wanted to point it out if that can be of any help.
Either sense (proxy) log or rest connector log should show multiple attempts I guess. I will also keep a closer look at my API calls.
well - I still don't know, but I can confirm indeed that one random app reload (or i should say NPrinting publish Task) trigger happend when i just duplicated app and jumped between Analysis/Data views (UI, load script).
In my case strange thing is that this also happens when reload simply runs from QMC Task.
I am more and more convinced that this has something to do with Qlik Sense behaviour.... lets keep an eye on it!
is the qvf you have sent me the exact one you are using to trigger your nprinting task?
Can you send me a qliksense task script log from the execution which triggered multiple metadata reloads?
or if you prefer we can take it offline. PM me and we may just quickly schedule a zoom to look at it. Cheers
yesterday I had a chat with @Vinn_Qlik and I reviewed his script. My conclusion is that the issue is sitting in Qlik Sense and the way Qlik Sense is handling reload tasks.
What we observed was that for all tasks where we had multiple "cache generations" in NPrinting we also had multiple attempts to run task by scheduler. This was visible in Qlik Sense monitoring apps when you look at the stages of particular reload task. It went through multiple stages and investigating it showed that task was "Triggered"-->"FinishedFailure"--> "Retry"-->(here on depending on the day there were multiple instances of "FinishedFailure"--> "Retry")and finally --> "FinishedSuccess".
In shor number of task executions in NPrinting was equal to number of retries.
I conclude this is not NPrinting issue or script issue. It is just something wrong with Qlik Sense environment (or maybe even it is working as designed). If @Vinn_Qlik wants to investigate further I guess he needs to open support ticket and work with support to troubleshoot those reloads with "FinishedFailure" statuses.