Hi All,
So I have a workflow I'm working on where I'm wanting to test and edit the flow but I have the outputs already setup. I don't want these outputs to be enabled as I'm testing and changing the flow and so I'm using the runtime option of 'Disable All Tools that Write Output'.
This usefully disables all my output tools, however, it also has the unintended effect of breaking caching parts of the workflow. You can select a tool to 'Run and Cache Workflow' still and Alteryx will run the flow but it never actually saves the cache. Furthermore, if you then select that same tool again you tried to cache, it gives the option to 'Clear Cache' on a cache it never created. Is this functionality intended?
Thanks,
Sam :)
Solved! Go to Solution.
Confirmed Bug
Reply from Alteryx:
Hi Sam, Thanks for contacting Alteryx Support - we have identified this as a bug and it is currently scheduled to be released in a version next year. Unfortunately I don't have an ETA on a fix, but I will associate your case with the defect so that you will be notified as soon as that release is available. Here is the defect number for your reference: DE18012. Best, Sophia Fraticelli | Sr. Customer Support Engineer Email: support@alteryx.com | community.alteryx.com |
I hope the bug is fixed soon. I can no longer cache & run in any of my workflows...which is a real PITA when it comes to using workflows that need a cache for development.
Michelle
Hello,
Just wondering if there are any updates to this bug? 2019.2 still has the same issue.
Thank you!
Starting with the 2020.1 release, you can use caching with the 'Disable All Tools that Write Output' option. Available here: http://downloads.alteryx.com/