We are celebrating the 10-year anniversary of the Alteryx Community! Learn more and join in on the fun here.
Start Free Trial

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Control container: Internal Error - Anchor was not closed

RexLi10
5 - Atom

Hi All,

 

My workflow has several nested control containers within a parent control container. In particular situation, user need to disable some nested control containers. In 2023.1.1.123 version, this process works normal, however, if my workflow run in 2023.2.1.51 or above version. The workflow crashed and pop-up an error message: "Control container: Internal Error - Anchor was not closed." I found another post in Alteryx community that described same issue. And the solution is to remove nested control container or ensure all nested control container is enabled. However, this solution is not suitable for me, anyone have another solution? Many thanks.

24 REPLIES 24
levell_x_dunn
10 - Fireball

I'm seeing the same thing, Control containers are having problems with Macros

 

 

"Error: Control Container (11): Internal Error - Anchor (11:Log) was not closed"

sowjanyayinti
8 - Asteroid

This is still happening and i am on the latest version. And yes, happening only when we use macros inside a control container.

I did notice something and not sure if this helps any of you. If your control container has a 'Select' tool then the anchor was not closed error appears. When I remove the select tool then no issues.

Attached screenshots for reference

nbondarchuk
Alteryx
Alteryx

Could you please share the workflow to replicate this issue? What version of Designer are you using?

sowjanyayinti
8 - Asteroid

I am on version Version: 2024.1.1.17. It will be hard to share workflow right now as it is a huge reconciliation workflow with internal data. However, the error occurred when I was using the Multiple Excel Sheet, tabs macro that was provided in the alteryx gallery. 

 

Now that I am typing this, I realized I didn't get this error when I used the same macro in a different workflow. I will try and mask the data and send the workflows in next day or two.

Div
8 - Asteroid

Here is a video that covers everything you need to know about Control Containers:-

https://youtu.be/ovZBB6eyqps

Check out my second episode on Alteryx Control Containers! Control Containers give you enhanced control over your workflows, allowing you to streamline and organize complex processes with ease. In this video, I walk through three use cases where Control Containers can make a big impact, from ...
Manderzrules
7 - Meteor

This is still a problem...Version: 2024.2.1.41 Patch: 1
I have multiple control containers within an overarching control container...each control container is only activated if there are records to be processed through those steps (filter tool to activate each internal control container)...if one of the control containers is not activated due to no records present, the overarching control container throws this error: Error: Control Container (837): Internal Error - Anchor (837:Log) was not closed


dgarmor
7 - Meteor

Can you provide a fix id, or version so I can update when available.  We are having the same issue.

marcus
6 - Meteoroid

I've just run into this. I was attempting to have a macro not complete its workflow if an input file was not found and after I wrapped all of my macros in a control container and added the conditions to trigger the container, the main workflow no longer works and I get this anchor error. I tested removing the control container and restoring the macro to the original configuration... and I still get this error. So now my workflow just doesn't work at all.

 

Edit:

 

So I restored backups of my workflow and all macros... macros that did not have control containers... and I was still getting the error. The main workflow had not changed. Does Alteryx cache a workflow once its run to speed up future runs? I finally fixed it by resetting the dynamic input's template file. I then re-set up my macros with control containers and everything is working as expected. 

_wlm_horton
7 - Meteor

March of which year?

TimPowers
7 - Meteor

Has the behavior of this tool been examined and fixed yet?

Labels
Top Solution Authors