When a dataflow runs long or has an error, you have to manually go to the dataflow settings, refresh history and download the CSV for more information. For appropriate refresh monitoring and trendin...
Agreed, we have an automated process that scrapes metadata vis REST API calls for both Datasets and Dataflows refresh history. It's frustrating that the Dataset refresh history includes the Failure Reason when a Dataset fails, but Dataflow API call for Transaction History does not include the Error reason. This would be hugely beneficial and make the REST API an actual useful tool for notifications etc...
