topic Re: Error Task Trigger Scheduled in QMC Qlikview Server May 2024 in QlikView

Error Task Trigger Scheduled in QMC Qlikview Server May 2024

abrahamparada — Mon, 26 Jan 2026 18:19:17 GMT

Hi friends, I had a problem when I updated Qlikview Server Vr. Nov 2017 SR6 to MAY 2024 SR1. Some apps failed to run in QMC. When I reviewed the logs, I found this Message:

PlanToGoOff - Skipped adding a new scheduled trigger state planned at 2025-02-05 00:30:52.000 since there is another still unhandled.
And
Triggers: Keep this trigger under observation: TriggerState[ChangedBy=1, Status=Unhandled, Planned=2025-02-05 10:24:47.000, ExecId=aa6775b2-fe59-4911-8877-70e32f252ad1, Trigger="ScheduleTrigger" for task "MON_E002_TaskLogError

Someone can know why this problem happens?

Thanks

Re: Error Task Trigger Scheduled in QMC Qlikview Server May 2024

David_Friend — Wed, 05 Feb 2025 16:21:22 GMT

@abrahamparada did you see the same issue in non-production testing?

Can you share the TaskLog and Document Log?

What does the task do? Is it a reload and/or distribute?

Re: Error Task Trigger Scheduled in QMC Qlikview Server May 2024

abrahamparada — Wed, 05 Feb 2025 17:50:17 GMT

Hi David, It does Twice actions, reload and distribute.

Sure, I'll attach the log

Thanks

Re: Error Task Trigger Scheduled in QMC Qlikview Server May 2024

Chip_Matejowsky — Wed, 05 Feb 2025 18:09:12 GMT

Hi @abrahamparada,

I count 6409 instances of the errors
"PlanToGoOff - Skipped adding new scheduled trigger state planned at YYYY-MM-DD HH:MM:SS since there is another still unhandled."
"PlanToGoOff - Skipped adding new scheduled trigger state planned at YYYY-MM-DD HH:MM:SS since there is another unhandled at the exact same time"

Are you seeing these entries every day? With this many errors in the QDS Root log, I'm wondering if there are file access issues with the Source Documents. Are you seeing any "Cluster_date.txt" files are written in the QDS ApplicationData folder?

Best Regards

Re: Error Task Trigger Scheduled in QMC Qlikview Server May 2024

Maria_Halley — Thu, 06 Feb 2025 12:54:45 GMT

@abrahamparada

In my experience this is usually caused by the taskresult.xml being locked by another process when the task is finished, so QlikView thinks the task is still running. This should be logged in the file @Chip_Matejowsky mentioned. Newer version of QlikView does read/write to file more often than earlier versions, so that is why you are seeing it now. Try to recreate the Application data folder, but if there is a file access/disk speed issue, the problem might come back.

https://community.qlik.com/t5/Official-Support-Articles/How-to-recreate-the-QlikView-Distribution-Service-folder/ta-p/1713724