Showing results for 
Search instead for 
Did you mean: 

Better more user-friendly error messages for failed flows

When viewing the run-log for a failed flow, it would be really helpful to tag or highlight the parameter causing the error in the step that failed - perhaps change the background colour to red, or put a pop-up user-friendly description of the error on an error icon against the parameter.


Having to hunt through JSON code when you don't really know what you should be looking for is very chancy.


Also, putting out error codes like "502 badgateway" is a bit meaningless - why is it a badgateway?  Is that a transient or permanent error, and what do I need to do to fix it?


This type of error message looks just like the error codes we used to get out of IBM Assembler 360 40 years ago... surely you can do better than that, Microsoft?

Status: Under Review

Thank you for the feedback, we will investigate how to improve this.

New Member


I am in the same boat. I'm running over 4000 rows and I would which row did not work. Simple as that!

Power Automate
Status changed to: Under Review

Thank you for the feedback, we will investigate how to improve this.

Advocate IV

And this shining example of gobbledegook from testing one of my latest scripts...

Unable to process template language expressions in action 'Send_an_email_(V2)_-_Subscriber_List_Audit_result' inputs at line '1' and column '2940': 'The template language expression 'json(decodeBase64(triggerOutputs().headers['X-MS-APIM-Tokens']))['$connections']['shared_office365']['connectionId']' cannot be evaluated because property 'shared_office365' doesn't exist, available properties are 'shared_sharepointonline, shared_office365groups, shared_office365users, shared_flowpush'. Please see for usage details.'.

Doubtless it means something to someone, somewhere, but in the context of quickly debugging my flow it's worse than useless.  OK, so I know what step is failing, but what input field is it objecting to?  None of the action parameters look anything like the names quoted so I don't have a clue.  This is like wading through a 1000-page mainframe hex-code core-dump when you don't understand Assembly language.