Skip to main content
10-Marble
June 17, 2026
Question

ThingWorx Analytics jobs stuck in “Waiting” state until another analysis job is triggered (ThingWorx 9.3.0-b20)

  • June 17, 2026
  • 1 reply
  • 13 views

Hi,

I’m using ThingWorx 9.3.0-b20 with Analytics Manager, and I’m facing an issue where analytics jobs stay in “Waiting” state for a long time.

This does not happen all the time, but occurs around 3–5 times per day.

The jobs only start running after I manually trigger another job (e.g., test an analysis model or create a new job). Once I do that, the waiting jobs immediately execute.

Expected: Jobs should start automatically without manual trigger.
Actual: Jobs get stuck until another job “wakes them up”.

Questions:

  • Is this a known issue in 9.3?
  • Any configuration related to scheduler/queue causing this?
  • Any workaround or fix?

Thanks in advance.

1 reply

Community Manager
July 6, 2026

Hi ​@A_10333884 

Could you give some more context on the issue; Are you submitting jobs in bulk? Are you running any Simulation jobs? Is the source event entity (or any parent entities) being modified? Are you using the instigating event for anything other than the Analysis Event?

You may want to try the workarounds from CS371311, namely to run the RefreshTriggerSubscriptions service in TW.AnalysisServices.AnalysisResourceProvider

I would also suggest opening a case with Technical Support for further help

Best regards, Nathaniel