If its a transaction record then there is a delay, specifically if the transaction is huge.
I have implemented a couple of things with after Submit + MR being called through task module where it was querying the same transaction and resulting in unexpected error.
Had to reimplement the approach, had a support case against it as well which escalated way too much.
Later after weeks of their investigation and architecture from NS ended up in the call with us. And we got to know about the delay and why it was resulting in unexpected error. (We were working on SO + Billing Schedule btw).
Haven't seen partial data being returned, but could be a possible issue.