Control container: Internal Error - Anchor was not closed

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.

AMP Engine

AMP-Engine

Accepted answers

nbondarchuk

Engine team has been fixed two issues related to the nested disabled Control Containers:

1. GENG-3404: Control container with nested disabled control container inside causes an error

2023.1.1 (Patch 6) March 7, 2024

2023.2.1 (Patch 3) March 14, 2024

2. GENG-3381: Macros that contain a control container and a nested macro with a relative path causes error

2023.1.1.336 (Patch 5) January 16, 2024

2023.2.1.89 (Patch 2) January 25, 2024

All comments

nbondarchuk

Engine team has been fixed two issues related to the nested disabled Control Containers:

1. GENG-3404: Control container with nested disabled control container inside causes an error

2023.1.1 (Patch 6) March 7, 2024

2023.2.1 (Patch 3) March 14, 2024

2. GENG-3381: Macros that contain a control container and a nested macro with a relative path causes error

2023.1.1.336 (Patch 5) January 16, 2024

2023.2.1.89 (Patch 2) January 25, 2024

pbibler

Does this mean the fix will come in March? Is there a workaround in the meantime?

nbondarchuk

Correct, the fix will be available in March.

A possible workaround is to disable all Browse functionality by ticking “ Disable All Browse Tools” checkbox in the Runtime tab of the Workflow window.

markashman

I am getting the same error on 2023.2.1.133. Have tried disabling and even deleting browse tools, no effect. Flow runs fine in Designer, but if I run as App it produces this error?

Has anyone got a solution.

cjclark

Hey all I am running into this in Version: 2024.1.1.49 Patch: 1, I have control containers with disabled regular containers in them.

pjarrard

Unfortunately, also having the issue with 2024.1.1.2.71 (Patch 2).

nbondarchuk

Could you please share a workflow example that represents this issue?

levell_x_dunn

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

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

Anchor Error With Select.PNG

No Error No Select.PNG

nbondarchuk

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

sowjanyayinti

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

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

https://youtu.be/ovZBB6eyqps

Manderzrules

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

marcus

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.

AshRez

it happened to me too and I am using Version: 2024.1.1.168 Patch: 5

I have Control Container that has a Macro, that same Macro also has "Disabled" Control Container. once I enabled it the issue is resolved and there is no problems. but if it was disabled I get the error "Control container: Internal Error - Anchor was not closed."

I need to created with disabled nested Control container because I need to prevent another issue which is "There is no valid metadata for the outgoing connection" for python tool.
Based on above, there will be never a resolution, eh!!

SupriyaKalluri

Anchor (200:log) does not closed

JamieHankins

I've been having the same error:

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

Some of my containers have macros in them, but some of those seem to run okay. However, others don't.

It can be very hard to work out what might be triggering the problem.

dataguyW

I was going to start another thread for this error, but it seems I'm not the only one having it. We are on 2024.2 and this problem still persists when having Tool Containers nested inside Control Containers. This seems like something that should be addressed and fixed as all of the best practices say to group your tool in tool containers. Because I can't say for sure when this is going to fail or work, I may need to tell my team to stop using these controls which is not a good practice, but I need the code to run.

Is there any official answer on this yet? It never failed in 2023.1.

JamieHankins

Yes, I'm now reluctant to use control containers in their current state: they're too unreliable.

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703