Power Platform Community Forum Thread Details

Question to the community: How do you handle what I would call 'ghost errors' when they are part of a solution delivered to a client?

Ghost error = an error that is resolved by deleting something and replacing with an identical replacement or no action - waiting until the error goes away.

More context:

I recently had this error for a flow:

"The input body for trigger 'manual' of type 'Request' did not match its schema definition. Error details: 'Invalid type. Expected Integer but got String.'."

This was a flow that had been working without any issues for months, no changes had been made and it was in it's own environment with very little if anything being changed, let alone anything that might directly affect the flow.

The error resolution suggestions within PowerAutomate included a category called 'intermittent error', in other words, the error comes and goes for no apparent reason. In my case, I replaced the manual trigger with the same thing (delete and replace with identical) and the flow began working. I'm glad it was an easy fix, but concerned that if this was a flow that had been provided to a client we would have to explain that 'sometimes Microsoft throws errors for no real reason'. For context, I have been working on the Power Platform exclusively full-time for 5 years and spurious errors are not uncommon.

I would be particularly interested to hear from people who are using the Power Platform as an ISV or in large organisations.

Thanks in advance!

Categories:

General topics