Let’s say I’m downloading a large file from the web, or I triggered some kind of local batch process that churns through a DB and emits an output file. Clearly I don’t know how long it’s going to take to fully arrive on my local disk before I can move along in my workflow.
If I use “Path Exists” right after I begin the download, it will fail. This forces me to either add a fixed “Delay” activity (always a bad idea)… or set up a loop where I retry “Path Exists”. Of course this forces me to also create and increment a counter to limit my retry attempts, etc.
Why doesn’t “Path Exists” simply have a timeout value (essentially a hidden retry under the covers)?
This would be huge.