How do I "reset" Orchestration

I am experiencing the same issue so I assume it must be a general issue

Mine is stuck on execution of a prepare instance

Hi ​@thzman ​@nmo 

Can you please try to stop the execution or flush the queue? Does this resolve the issue?

To do so please select Process Management

And then select process queue

I have tried to to use both functions several times without any results.

I have also tried to restart both ODX and execution services.

No jobs are running, and it seems to run fine if I start the jobs manually in the TimeXtender desktop client

I have restarted the ODX service, but I have no such option under Exception Manager in the portal (no small triangle on the side of the menu item).
Probably because we are using the free version?
 

​@nmo ​@thzman the product team has informed me that this is an intermittent error, which should now be resolved. The product team is currently investigating the root cause of the issue.

​@Christian Hauggaard 

I had the exact same issue happen tonight again.

The proces got stuck on the execution on the same MDW as last time, even though the MDW execution package completed in the regular time when viewed through the TimeXtender client.

Only difference is that this time I am not able to restart the remaining steps through the Exmon map, but rather I need to manually start them through the TimeXtender client

I am still unable to stop executions or flush queue in Exmon

We had this last week too, and facing exactly the same issue today. Process in Exmon hangs while the execution package has finished hours ago.

Flushing the queue does not seem to work. There are still packages from last week in our list that has been stopped/flushed before.

Having the same issue today again. Was uncertain if it was due to me upgrading to the latest version yesterday but I suppose it’s not then. I’m having the additional issue that the jobs are in a “waiting” state so I can’t even start them manually. Have run the service configuration multiple times but to no avail.
Restarted the server the services are running on and ran the configurator again.
Now it looks like this:
 

What is happening here?
Exmon still looks like this:
 

I am wondering if it could be related to running on the previous version of Exmon?

I am still on 24.2

nmo wrote:

I am wondering if it could be related to running on the previous version of Exmon?

I am still on 24.2

 

We’re running on 24.3.0.49 and facing the same issue.

Same version here:
 

How do I fix these jobs stuck in “Waiting”?
 

I’ve run the execution service configuration a number of times but it doesn’t do anything.
I’ve uninstalled all old version of the execution service
I’ve restarted the server twice.
I even installed the execution service on another server to forcefully move the locks for these jobs.
Feels like I’m running out of options.