Happy 8th birthday to the Maveryx Community! Take a walk down memory lane in our birthday blog, and don't miss out on the awesome birthday present that all Maveryx Community members get to take advantage of!
I designed an Alteryx workflow in Alteryx Designer 2021.3 for performing records match using the Fuzzy Match tool and ran fine without any issues. Our client informed that it's not an Approved version for our client and so downgraded it the lower version Alteryx Designer 2020.4.5. The workflow designed earlier is failing (Fuzzy Match) with below error when tried to run in Designer 2020.4.5 version.
Below are the User settings and System settings in the Designer. Please help me to fix this issue.
Thanks Mike! I was coming to ask the same question. For sure we have fixed a number of memory deadlock issues with AMP up until the 22.1 Release. So if this workflow is AMP enabled, I would recommend saving it without "Use AMP Engine" checked in the Workflow Configuration - Runtime settings and see if that helps.
Tonya Smith Sr. Technical Product Manager, App Builder and Alteryx Marketplace
Thanks Mike and Tonya for the response. I ran the Alteryx Workflow and App without "Use AMP Engine" (uncheck the option in Workflow Configuration) and the workflow ran fine without any issues.
But, I have a huge amount of data (~2 million) on which the Fuzzy match needs to be performed and without using the AMP Engine, it's taking a huge amount of time (4-5 hours) and that's the reason I was using the AMP engine. Is there any other way I can run the workflow using the AMP engine without "Out of Memory" or any other errors?
Also, I tried to publish my Analytic App in the Gallery and received below error. Can you please help me on this.
Unless you upgrade, your only option here is to go non-AMP. Otherwise you'll get the memory issue.
For the "Cannot access" errors, either the "Run As" account must not have access to wherever the files are located. This is common on secure networks. You personally may have access, but the 'server' does not. First you have to find out which credentials the server is using, and then get those credentials access to the locations.
For the SQL Server error, it sounds like the same issue.