Control container: Internal Error - Anchor was not closed

[RexLi10]

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.

[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.