We have multiple instances of our app connected to your OTS service, and we have noticed that validation results are being sent to random streams. For…

instance, we may receive results in instance #1, even though the validation request was originally sent from instance #2. How can we address this?

Issuing a request, for example, TicketResult, from any of your OTS-connected instances will send the response from the server to all of the instances. This is a feature, not a bug; we do not support any instance separation, as is the case with the odds feed (AMQP with the possibility of node_id). The model of cooperation with betting platforms predicts either one production feed + OTS per platform, which then gets distributed to end clients, or a separate odds feed + OTS account for each end client.