Control Containers - Anchor was not closed issue

[Krishnasn]

In a workflow, where I have multiple tool containers with In-DB tools placed within a control container, I'm encountering the error: Error: Control Container (171): Internal Error - Anchor (171:Log) was not closed

It doesn't appear when I remove all the tool containers keeping the tools as-is and having them all in the control container.

But this makes the code unorganized and hard to read.

Any ideas/workarounds would be appreciated

Thanks,

Krishna

[john_watkins]

I have some odd issues with In-DB controls and control containers, but usually it is around flow control.  I know you can't go from one control container to another if there are in-db objects  directly linked.  I don't see that in your workflow though.    Make sure you are referencing the exact same connection on the in-db.   I will get issues if I use file connection that references a direct path C:\whatever vs. a UNC \\myPC\whatever.     When the tool containers get heavily nested I normally just get a big red X on my screen.  

Not sure if this helps, but I'd like to stick around for the final answer.

[Krishnasn · Accepted solution]

Hi John,

Appreciate your response.

I agree with you when you said the nesting of Tool Containers could give this issue. I removed the nested Tool container (The Dark Blue one) but still was getting the error. When I removed the Tool Container (Light Blue one) enclosing the Connect and Dynamic Input In-DB tools, then my workflow ran fine. Pls see the Attached screenshot.

Also, I starting getting this error on introducing the Dynamic Input In-DB tool to my workflow. This could be a related reason too.

I would still wait for an answer from experts here. 

But I definitely agree that nesting tool containers inside a control container used to give errors. It was mentioned as resolved as part of a patch in March 2024 - Control-container-Internal-Error-Anchor-was-not-closed