Sentry Node JS exceptions catched on the wrong transaction

Question

We are trying to use Sentry as a tracking system in a Nest JS based application that is using a microservice architecture. So far we haven't been able to setup the performance correctly. What we are seeing is that for some transactions we have errors not related to the transaction The transaction with errors do not belong to the user that generated them One explanation we have came up with is that the initial transaction is sampled and the server receives new requests that are not sampled before the sampled one finishes, therefore exceptions in those not sampled transactions are catched with info from the current transaction. But all this is speculation.