Release v4.54.0 into master

specification/documentation/CreateMessageBatch.md

@@ -17,7 +17,7 @@ The per message reference (`messageReference`) needs to be unique within the mes
 
 You may be required to send through specific personalisation fields based upon the routing plan (`routingPlanId`). These will have been setup during your [onboarding](#overview--onboarding) process.
 
-These are not validated when we store your message batch, but will be validated when we attempt to send the messages according to the routing plan. If there are values missing from this then the messages will fail to send.
+These are validated according to the routing plan when we store your message batch. If there are missing values then the entire batch will be rejected with a `CM_INVALID_VALUE` code. The detail and source fields will provide further information about the error.
 
 ### Sandbox
 

specification/documentation/GetMessage.md

@@ -24,7 +24,7 @@ Key values that are returned for each of these channels are:
 * `channelStatusDescription` - the channel status description
 * `channelFailureReasonCode` - the channel failed reason code
 * `supplierStatus` - the status provided by the supplier for this channel
-* `retryCount` - the number of times we have attempted delivery
+* `retryCount` - the number of times we have attempted delivery, only returned if sending is retried one or more times.
 * `timestamps` - timestamps of key events
 * `routingPlan` - the routing plan that was used to generate the channel
 

specification/snippets/RetryCount.yaml

@@ -1,3 +1,3 @@
 type: integer
-description: Contains the number of times that we have attempted to send this message to this channel.
+description: Contains the number of times that we have attempted to send this message to this channel. Only returned if sending is retried one or more times.
 example: 1