Task is stuck in the Starting email variables resolution

[MANIDK]

Hi All,

Our Nprinting task is scheduled for every 30 minutes from 7 AM to 9 AM.

The scheduled task for 7:00 AM was successfully completed, but the task for 7:30 AM still had the running status after 20 minutes. We had to manually abort it. Then, we go through the NPrinting log, but only we can see the resolution of starting email variables.

Below, I have attached the log screenshot.

Could you please provide me with the solution for this issue.

Regards,

Manikandan

[Lech_Miszkiewicz]

Not much we can comment about that. 

We would need to see logs to say more including information on what was happening on Qlik Sense server at the time as well as NPrinting server. 

The other thing is we would need to know more about your setup: detailed info about hardware and software of both (Qlik Sense and NPrinting servers)

The fact that something is stuck indicates to me that you are:

• have some unsupported objects in the app
• Qlik Sense app was reloading when you tried to run report - for such frequent tasks run you normally would use API calls to make sure NPrinting runs only after Qlik Sense app reload and as soon as Qlik Sense i reloaded (API chain)
• you have unsuported configuration not meeting requirements from help site
• you run some other software on one of the servers
• you have network issues

All requirements are on https://help.qlik.com !!! Please study it thoroughly as there is a lot to consider. 

For now we know that you have a problem, we acknowledge it and we can say as much as I said above as we have to little info to suggest more detailed troubleshooting steps. If you could share more details about your setup and configuration maybe we can suggest something...

cheers 

[Frank_S]

As mentioned, unsupported items are a 'very' strong possibility.

Check into these as they are described in detail here:

https://help.qlik.com/en-US/nprinting/February2024/Content/NPrinting/GettingStarted/HowCreateConnect...

Further, suggest that you review your the underlying formulas in your variables. There is a possibility that they are simply not resolving the information that you are trying to extract.  

So test your variables thoroughly to ensure they are working as expected and that the underlying data is actually there in your data model available to be resolved by your variable (and the underlying formula therein).

If the variable cannot be resolved, the task likely will not proceed (as you are seeing but it will eventually time out). Check the NP engine and schedule logs for variable could not be resolved errors.

Kind regards....