When calling multiple oData requests within a batch request which contains a final oData action call F&O will not return any errors prior to the oData action but instead run the action and return the result from that.

This is does not follow the oData protocol which is that the first error encountered should be returned to the caller. Nor does it follow the behaviour of the same API's when the oData action is not present, as in that instance the first error will be returned.

It seems an inconsistency in the behaviour of the batch that it won't process API calls after an error but will still attempt to run the oData action.

Can this inconsistency be resolved as otherwise it's not possible to incorporate oData action requests within a batch call.