This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
It would be helpful to have one of the following methods to disable output modules to prevent overwriting output files each time a workflow is run:
- A global 'Disable All Output Modules' option, which would effectively mute the workflow without removing any connections
- A module-specific 'disable/enable this module' option, to the same end
Something like this option ? 😉
Ha! Yeah, something like that. Duh.
No worries. If only they were all that easy 🙂
Ok, but what if I only want to overwrite a specific output? I have a workflow using a large amount of data, with multiple outputs. And when I need to rerun a specific section of data, I don't want the other unaffected outputs to overwrite the database with NULL values.
I would recommend using a Tool Container for each section of data. For each container, you can disable it causing it not to run while the rest of the workflow runs.
Here is an article that talks more about using Tool Containers and how to disable them:
I want to disable In-db output tool. Can anyone tell me how to disable in-db output tool since the above method does not seem to work.
What happens when you don't have that option?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.