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's the most wonderful time of the year - Santalytics 2020 is here! This year, Santa's workshop needs the help of the Alteryx Community to help get back on track, so head over to the Group Hub for all the info to get started!
Hi I am fairly new to Alteryx and have an issue with the use of the Block Until Done tool. I have seen several posts on the issue this and a solution of a parallel blocking have been proposed but not sure if there is a seperate Alteryx tool for this. In summary what I am trying to do is for the workflow to extract 3 files from 3 processes and once this is completed, I like extracted output files to FTP to another server. Please see the attached screenshot of the workflow. What seems to be happening is the FTP process is starting while one of the file is still being created. Any help/guidance would be appreciated as always. Kind Regards Naresh
@nbarai I don't see an image attached, but I'm imagining you're seeing that happen because the Block until Done tool is sensitive to the order in which it is added to the workflow when using multiple. If you have to use multiple Block Until Done tools, they will run in the order they are added to the workflow, so it makes sense to label them as you put them in.
The always amazing Parallel Block Until Done tool can be found in the CREW Macro Pack. It's a lot easier to use and takes all the guesswork out of things.
From my experience, the block until done tool only applies to records being PASSED through the tool, not OUTPUT via an output tool after the Block Until Done.
A stream is ended with a Block Until Done (BUD) tool. From connection #1 of the BUD, you have an output tool. From connection #2 you have another bunch of tools. Your connection #2 tools will in fact begin processing once all records are PASSED from #1 to the output tool, even if the output isn't fully finished. So in essence the connection #2 tools will process before the output from connection #1 is created. Of course, it all depends on the output being created. For small outputs, it's not an issue. But if you're outputting gigs of data, then it becomes an issue if the 2nd connection is dependent on the first one being complete.
Correct, no native Alteryx "tool" will do this. If you want to use native functionality from Alteryx, then you'll either have to use the run command event for this (if it's a YXMD), or the chained app functionality (if it's a YXWZ).