Control Containers still run in disabled containers
- 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
Apologies if this has been posted before, I've looked through the forums and cant see anyone else mentioning it.
I've noticed recently that control containers still run when in disabled standard containers. Is this expected?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
@glenebb I see the same thing, and I don't imagine this is expected behaviour.
I would log a support ticket with Alteryx through mission control to notify them
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hello @glenebb, on which version are you experiencing this issue? Similar to @OllieClarke, I am also experiencing this issue with the identical setup you shared in the screenshot.
My Alteryx Designer version is 2024.1.1.93 (latest version with the latest patch), however this might be also present in other versions of Alteryx Designer (from 2023.1 onwards), I am aware that similar issues were found and then resolved but this seems to not be resolved yet, at least in the latest version and the version you are using (which might also be the latest version).
You can check your version from Help > About.
A workaround is to nest the Control Container inside another Control Container (instead of a regular Tool Container) which is disabled, which seems to work fine on the version I mentioned (Append tool produces no outputs).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
@NeoInfiniTech from my testing it appears in version 2024.1.1.17 and version 2023.2.1.173 Patch: 4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Thanks for testing, @OllieClarke. While many bugs regarding Control Containers were fixed, this is one that doesn't seem to be fixed yet. Thank you @glenebb for bringing this to attention and the best course would be to open a support ticket as @OllieClarke mentioned.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Simply disabling the control container stops it from running which is an easy fix. It's just that i only realised after i found a db had data which it shouldn't 😂
I've logged a support case and this is their response:
This issue has been logged as a defect (GCSE-2515 ) and passed on to our development team.
