Macro re-enabling files that write output

[JTCairns]

Has anyone ever came across this issue? i have a standard macro that I'm developing. I select "disable all tools that write output" but when I run the macro it deselects that box?

[danilang]

Hi @JTCairns 

When you use a macro in a workflow, the engine will use the runtime settings of the workflow, ignoring those in the macro.  Is this what you're seeing.

Dan

[JTCairns]

Hi dan

No, when developing the macro itself it change the engine settings but if I open the macro for testing the runtime settings have changed and if I put them to disable all tools that write output this changes if I hit run.

Thanks

[danilang]

Hi @JTCairns 

Hmm.  Same behaviour here.  It's not something that I ever noticed before.  Part of my routine when opening any workflows, apps, macros is to check and disable any outputs if required.  

I'm not sure if you want to open a support case for this. 

Dan

[JTCairns]

yeah i may do it seems an odd behavior that i haven't noticed before

[patrick_digan]

@JTCairns did you end up submitting a support ticket? This sounds like a bug that @Kenda ran into and I confirmed is an issue.

[Kenda]

I have an open ticket with support right now. Hopefully they can fix soon as this could lead to some data being overwritten accidentally! 😰