Recently we faced a locking issue in BC caused by a Power Automate flow that was triggered by a record change in BC: we were not able to run any job queue because of this error message.

The flow was dependent on a field that was obsoleted by update of BC (18.3 > 18.4).

Finally the solution was quite easy by removing this field from the flow. But the problem was that we did not get any notification or warning that updating BC to 18.4 would cause a Power Automate flow to fail and block processes in BC.

It would be great to have check on Power Automate flows that are connected to BC in order to verify if the flows are still compatible when BC updates are executed. Something similar to 'Automated testing' protocol for BC extensions.