Workflow stuck in "Initializing status"

Hi,

Every now and then, I see workflows that are stuck in the "initializing status" in the queue.

I can't delete it. So I'm forced to restart the worker/controller, or in some cases, it fixes itself without any input from me.

Has anyone else experienced this behavior? What did you do to fix it?

Thanks,

John

Initializing error1.docx

Workflow

Error Message

Server

MongoDB

Accepted answers

All comments

MarqueeCrew

@JohnBell ,

I can't say that I've ever had this happen. When you say that you restart, are you actually restarting or are you using TASK MANAGER on the server to stop and start the service? That could be faster.

I worry that the MongoDB entry might be set that the job is running and you might only be running a limited set of concurrent jobs. If that is the case, you'll need to cleanup the MongoDB (support@alteryx.com).

Cheers,

Mark

JohnBell

I'm actually restarting the Alteryx service.

AlteryxSupport initially told me that it's stuck in "initializing" is due to communication issues with the controller/worker due to over-utilization.

But I'm wondering if this is common? Because when the "initializing" error occurs the server isn't experiencing much activity compared to other times of the day.

Thanks,

John

sd83893

We are experiencing similar error "Initialization" Status....

levell_x_dunn

Hi @JohnBell ,

Unfortunately we see the same issue.

We have 1 controller and 5 workers so we have plenty of space but now and then Alteryx goes buggy and the workflow gets stuck in initializing and it will stay there for days if we don't restart the service or sometimes the entire server.

Which is a problem for us since we have jobs running 24 hours so there is always at least one job on each server. So we have to fail someones job just to restart the servers.

Alteryx hasn't found a fix for this yet.

DawnR

We have similar behavior. Currently running 2018.4. No solution has been found - it's really annoying. Hoping our upgrade to 2019.3 reduces some of these kinds of challenges, but I'm not feeling confident that it will.

DawnR

Still an issue after our upgrade to 2019.3.

NeilJ1

We intermittently see this problem too (on 2020.2 but also saw it on earlier versions). We run quite a lot of stuff on the server each day and only see this problem once a month or so on average, so it's not a huge issue but it is a little annoying because we only tend to find out that it has happened when a user contacts us to report that something they are expecting hasn't run.

The fact that we have to restart the Alteryx service to rectify this is also a pain. I wouldn't have thought it would be beyond the wit of man for Alteryx to build a fix for this that sees if a job has been initialising for x amount of time and if it has either a) kill the job and send an email to the admin user or b) notify the admin user and enable the cancel/delete button for that job.

Shaaz

Hi, Were you able to get a solution for this ?

yuriy

Having the same in 2022.1. Any solutions?

Also found a KB article about this that lists Reason: Unknown. And remediation is supposed to be deleting the jobs from the queue. The problem is that I can't delete these jobs. The delete button is grayed out. I am able to delete other Running jobs, but not the ones that are in Initializing status

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703