Urgent! Workflow stuck in Queue
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Help! I hvae a workflow stuck in the Queue window of the Scheduler since just after working hrs last night. It held up all of our overnight workflows from running. I am not trying to delete the item in the queue. I got the name to disappear by deleting the workflow in the schedules window, but that is as far as I got. The workflow is stuck at 66%. What can I do to knock this one off so it will move to the others?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I would call or chat http://www.alteryx.com/support with Alteryx. There is a record in your scheduler database that is holding up the processes. A restart may fix the problem, but I'd get with support if you are "URGENT". Since you don't want to delete the queue, an edit to the database might be the answer. When you contact support, let them know that your production processes are down (you can't run production work).
Thanks,
Mark
Chaos reigns within. Repent, reflect and restart. Order shall return.
Please Subscribe to my youTube channel.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hey Mark.
It was resolved with a manual reboot of the machine. I would have started with that, but I saw the emails as soon as I woke up and jumped on to our machine that houses the scheduler through remote desktop, which doesn't give me the functionality to restart the machine itself.
When in doubt... reboot! Thanks again for the link, I had forgot about how accessible the help desk is here. In the end, they weren't able to do much for me until someone got in the office to reboot, but it was a good suggestion none-the-less.
Thanks again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Chaos reigns within. Reflect, repent and reboot. Order shall return.
Chaos reigns within. Repent, reflect and restart. Order shall return.
Please Subscribe to my youTube channel.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
After all these years the old "reboot when in doubt" is still at play! LOL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
+1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Is there an alternate solution to this issue? I am running on a single server virtual machine, and just executed an upgrade from v2020.1 to v2021.3. You can see in the attached image that our location is encountering the same issues. Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Diable AMP and republish the workflow - This worked for me.
