According to the ADS documentation the 'A27 Message Ordering' error occurs as follows:
'The ADS sends this status text to the sink application when the ADS receives image data before the image header from the ADH. Such a situation can arise due to the fact that RRCP does not guarantee the ordered delivery of messages between broadcast and point-point streams. Such a scenario is more common if the ADS and ADH are on the same host.'
The suggested workaround is 'Setting *usePointToPointData: False in rmds.cpd tells the ADH to send images by broadcast, which should reduce the symptom (though at a cost of increased broadcast traffic).'
As this is a TREP infra issue, If you continue to have this issue, I recommend your Market Data team to raise a support ticket with our TREP Infrastructure support team who may be able to assist further.
It is not clear from your question what issue you are actually facing.
Can you please provide some additional details & context for what exactly is going wrong and what you are trying to achieve?
Please provide any log output or status messages etc so we can understand and help you better.
The symbolist output is in terms of many messages, each is a partial refresh, until it completes. When the number of partial refreshes is large, the client via adh/ads may only receive some of them then get (Text: "A27: Message Ordering Error. Recalling.")