Hi,
I got some "Anchor was not closed" internal errors when the AMP engine was enabled on a working workflow. I would appreciated it very much if anyone can help resolving the error. Thank you!
@pxs132 Thank you for using AMP Engine.
Would you be able to provide a screen shot of the Summarize tool configuration please?
Thank you. Here are the screen shots:
Hi @pxs132
I did find a known issue that we already have logged related to Anchor was not closed internal errors with AMP. I added a link to this post to that issue in case it is related so that we can additionally try testing this issue with the fix.
I'm having this issue as well in Designer 2021.4.
If the AMP engine is on, I get the error.
AMP off, no issues.
Was this ever resolved for you @pxs132
@gpmyers111 is yours also related to Summarize tool?
It seems this is an issue that needs to be fixed tool by tool. We did fix it for multiple tools in the past: Sort, Tile, Record Id and Batch Macros. But I did not find an existing open or fixed defect with Summarize tool. I would need a workflow to reproduce and then I could create a defect. If you can provide a yxzp you could email it to me at tonya.smith@alteryx.com
Mine surfaced with the Batch Macro tool. It's a workflow I've had in production for some time and it runs just fine on the E1 engine, but when I turn on the AMP engine, everything downstream from the Batch Macro tool throws this error. If I turn AMP off, it goes away and works fine.
I did find some fixed defects related to Batch Macros with this error, so I would need a workflow yxzp (or macro) that can be used to reproduce the issue in order to look into it and create a defect to fix.
Has anyone here tried enabling the "Engine Compatibility Mode" with these workflows to see if that helps with the error? Is this error seen in Desktop Designer as well as Gallery or just in Gallery?
Having the same issue, but with AMP engine turned off. The Union tool fails. Have tried to merge the data small pieces at a time, with extra memory to Alteryx, with AMP on, with AMP off, with Auto Field data cleanup
@MikeD That sounds like a different issue than this post. Would you please either create a new post for your issue or contact Support?
I had this issue with Summarise tools. Using the Engine Compatibility mode seemed to resolve the issue for me.
I'm getting this error on the Summarize and Join tools. The AMP Engine is turned on. This error causes the workflow to abort output and claims it is "User Canceled" The screenshots below show the portion of workflow where one Summarize and two Joins are björked, the configurations for each are included. If I turn off the AMP Engine, the workflow executes fine but takes FOREVER. ×__×
Thanks Tanya - turning engine compatibility on for the AMP workflow resolved the issue for me.
Nothing seems to work, so I had to delete the Control Containers finally.
While I came across this error rather recently and found that it might be happening for a number of different reasons, mine was related to Control Containers like you @harvjul.
I came across two different Ancor was not closed errors, one for which I created a support ticket and it was accepted as a defect (which will be fixed in the future): If you nested one or more control containers within a parent control container and one or more of those are disabled, the workflow will error until you enable, delete or move these control containers out of the parent control container.
Another scenario I came across recently is that if you use a Run Command tool in a Control Container without using the "Read Results [Optional]" functionality, you will receive the same error message "Anchor was not closed". Creating a placeholder csv file and defining it as your "Read Results [Optional]" file or using the output you created using the "Run Command" tool works fine though.
Is your error related to any of the situations listed above?
I had the control containers inside another regular container, that was turned off. After checking the data, I turned on the regular container to output to the Sharepoint Lists stored in the control containers, and that is when the error occurred. I am still using the deprecated Sharepoint List tool, as our IT will not approve the Sharepoint connector.
Four years later and the issue still isn't fixed? I'm not even surprised at this point @Alteryx
