scheduler getting stuck on block until done tool?

[MartWClimber]

This morning we had a very strange error.

some of our workflow chains didn't run over the weekend and were still running.

normally all of these workflows take 1 or 2 hours max. 

I did some investigations and it looks like that either the block until done tool was holding the data or data was being held between Alteryx and Azure (because the files in Azure didn't update).

because I myself don't use the block tool that often I was wondering if people got similar experiences with this tool that it indefinitely blocks.

if that is not the case i need to start looking in the between Alteryx and Azure to see why data is not being pushed 

[salbol1]

Many times when I'm invoking Block, I run it in combination with a Test tool and condition that needs to be met prior to the other output arms running - as well as tying in "Cancel running workflow on error" if the test does error. I've seen leakage in that tool where the other prongs will actually run prior to the first logic path completing, in as much as writes to downstream databases has occurred when the test condition actually ends up in a fail. I've found unless I use these in combination, that tool doesn't behave as you'd expect it should. 

I know this may not address your situation directly - but just some observations and methods used around this tool.