AMP engine - Anchor was not closed
- 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
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!
- Labels:
- AMP Engine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
@pxs132 Thank you for using AMP Engine.
Would you be able to provide a screen shot of the Summarize tool configuration please?
Sr. Product Manager, cloud App Builder
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Thank you. Here are the screen shots:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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.
Sr. Product Manager, cloud App Builder
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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
Sr. Product Manager, cloud App Builder
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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.
Sr. Product Manager, cloud App Builder
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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?
Sr. Product Manager, cloud App Builder
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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
![](/skins/images/BADF6AA807F6DD3B2FEB7AF2AFB4E176/responsive_peak/images/icon_anonymous_message.png)