Disable outputs keeps turned back off

[leonhekkert]

I have a flow in which I'm developing, so therefore I've checked the 'Disable all tools that write output' option.

However, when after I run the flow the option is no longer checked. What can influence this? I thought default behaviour is that it's turned on until you manually turn it off again.

[aatalai]

@leonhekkert not sure why this is happening, but just as a heads up if you check the disable all outputs and using something like sharepoint output that would still right. 

A possible work around could be putting your outputs in a container and then disabling them like so

[leonhekkert]

Hi Aatalai,

thank you. I'm aware. But in flows with 10+ outputs thats not desired. So I would like to keep using the option to disable them all at once.

[aatalai]

@leonhekkert is it please possible to have a screenshot of the workflow (and to confirm these are green output tools or orange render tools you have in your workflow - i.e not a connector and not embedded in a macro)

[aatalai]

@leonhekkert you could also put all the outputs in one container and just disable that one? appreciate it is non optimal but a possible work around/patch over nonetheless

[leonhekkert]

Sorry, cannot upload a screenshot.

@aatalai thanks for thinking along, but I really need the normal option to work here. :)

[aatalai]

ok @leonhekkert does this option become unchecked after you run it?

[leonhekkert]

@aatalai, thats the one.

[KGT]

If that's happening and it's repeatable, then that's a bug. Log it with MyAlteryx up the top of this screen. You will need your version etc, as that's really important.

I understand what you mean, by wanting that option to work. I may have used it 3 times in 7 years of Alteryx, then in my current role, I've used it multiple times a week for the last 2 years. Disabling containers is fine on a 50 tool workflow, but not 200 tool with 10 outputs. I would be furious if that happened and the output was to overwrite delivered results. I've had it happen before that we've overwritten results, by someone not ticking that, and it takes a little time to wind it back and recreate the result off the published files. 

[Diederik_vanderharst]

Hi @leonhekkert , I wouldn't be surprised if somehow the workbook XML got corrupted, causing a setting to default.
My suggestion would be to copy the contents of your flow to a new workflow and see if that resolves your issue. If the issue doesn't repeat it self, and your "copy" works as it should, then overwrite the old disfunctional flow with the new one. Let's hope that solves it for you.