how is it possible to have the job stuck with status “waiting”, and if I try to manually run the job, I get the error “job is already queued“
i’m running TX version 6675
![](https://uploads-eu-west-1.insided.com/timextender-en/attachment/493b0074-29f0-4ea4-9991-2513651f0602.png)
how is it possible to have the job stuck with status “waiting”, and if I try to manually run the job, I get the error “job is already queued“
i’m running TX version 6675
Hi
Hi
EDIT: updating to 6691.1 seemed to solve the issue, but maybe just as a result of the upgrade process.
I am experiencing the same or a similar issue with jobs that do not want to start:
Interestingly, I also have a job with a blank ‘State’ and an execution status of ‘Running’. There are currently no tasks in the ODX execution queue/log and no execution packages running in the effected instances.
I tried restarting the execution service and ODX Server service, and running the configurator again for both, but the statuses remain unchanged.
Kind regards,
Andrew
Hi,
Any update related on this topic? I am experiencing the same in my DWH where I schedule/ execute jobs with the Exmon Orchestrator.
Below an example for “Waiting” status for already 2 hours.
Updated TimeXtender to the latest version 6698.1, rebooted the services and server but did not fixed this issue for me.
Kind regards,
Devin
Hi Devin,
I haven't encountered the issues in 6698.1 anymore. Did you run the execution server configurator again?
Kind regards,
Andrew
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.