Qlik Sense command JobTriggeringService error

Hello,

Sometimes the job-triggering service for Qlik Sense raises an error, causing the EasyMorph project to stop. We would like to avoid retrying the entire EM task for memory-intensive projects, so what would be the best way to retry only the Qlik Sense command instead of the full project?

I tried creating two modules: one containing only the Qlik Sense command action, and another that iterates this module with "Collect errors and continue." This second module is called from the main module using a repeat action limited to 5 retries. However, it seems that the task is not launched in the QMC (although it runs fine when I manually execute the Qlik Sense command action from the module).

Thanks and best regards,
Chris

Hi @Chris,

Can you post a screenshot of the error generated by Qlik Sense?

Also, did you try adding a pause (using the "Wait" action) between retries?

Hi Dmitry,

Indeed, I tried with a pause of 5 seconds.

And the error log file :
30-09-2025 06:00:00.806 000036 INFO call RunSessionManager to run RunSession in Async mode
30-09-2025 06:00:00.806 000037 INFO BEGIN action "Qlik Sense command" in table "ACC.GroupeUtilisateur.qvd", step 1
30-09-2025 06:02:01.260 000038 INFO Enter RunSessionEvent::Stopped handler
30-09-2025 06:02:01.260 000039 INFO runsession state Aborted
30-09-2025 06:02:01.260 000040 INFO cleanUp called

The error indicates that Qlik Sense didn't respond for a long time (>120 seconds) and the action failed. It's hard to say why Qlik Sense doesn't respond.

Are the credentials configured in your Qlik Sense connector still valid? E.g. password not expired, etc.

Also, please confirm that the task has no timeout configured in the task settings.

Hi Dmitry,

It happens randomly on tasks that run fine after a failed attempt. I don’t see any clear reason why. Our QMC is configured to run 4 tasks simultaneously, and any additional tasks are queued. Could this be the cause?
Is there a way to disable the 120-second response time limit for the action? We haven’t changed the timeout setting of any EM task, so they are all still configured as “No”.

We’ve increased the timeout in the Qlik Sense connector from 120 seconds to 300 seconds (5 minutes). You can download the updated version from our website.

Ok, thanks — we’ll give it a try. Is there a way to configure the timeout in the connector (which might have a default value of 300 seconds) instead of having it hardcoded?

Not at this point. We will add a setting for it later.