It would be helpful if error messages were more descriptive helping the customer understand what is causing it and making it easier on how to address them properly. Especially, when these errors are part of a changed rolled out after an update.

According to the customer:

"I would hope that this information gets passed on to the appropriate people at Microsoft so that error messages are more strongly pointed to the issue as opposed to a bunch of JSON that most no-code/low-code users wouldn’t have any idea how to decipher. For instance, “Child flows must be turned on before the parent flow can be saved.”