This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Over the past couple of days very annoying thing happened. I'm working on my workflow, not doing anything exceptional, and suddenly Alteryx freezes. You don't get any information from OS that the Program is busy or waiting, it doesn't get the white overlay. I can still see my workflow clearly but nothing is clickable, and you can't interact with any part of the window.
The only way to close it is to kill all Alteryx processes in Task Manager and start any unsaved work again.
My memory sits below 50% at the moment, CPU way way lower (16GB RAM, 2.8 Quad Core).
I had a issue with 10.0 when I had browse tool selected and hit run - it would run but then freeze. Once I stopped having a highlighted browse tool selected before hitting run and it would not crash - it was not ideal but prevented the crash.
This issue was fixed in 10.1.
Now in 10.1 I have a crash issue when I double click a prop/result window to un dock it. I have sent my info to support and guess I will have to wait for 10.1+. This was not a issue at first but I have a laptop with dual monitor setup at home and work which are a little differnet and this seems to happened once i setup home.
Also I recognise your premise about the environment, however it happens even when doing the simplest tasks (without running anything in the background). What is weird is that is not a usual irresponsive software (the window being full opacity, no overlay, just nothing clickable. The process is also running fine in task manager
We have now received many reports of this same thing occuring and are aware of the issue.
Development was able to replicate occasionally but could not get a consistent demonstration of the problem. We worked with several users to get as much information as possible and we now believe that we have the scenario as well as the problem figured out. We are testing a resolution now and hope to provide a patch release in a couple of week.
We experience this too very often - my solution to the problem is to just leave Alteryx to do its thing and run in the background come back 5 mins later and usually it's responsive again. Most of the time this works.