There is no guarantee when the second message will receive a message, but the atomic scope definitely doesn’t have to finish immediately. It even has a timeout property!
The engine doesn’t dehydrate the orchestration while within the atomic scope, and this eats some resources.
Otherwise, I also don’t understand why this restriction on atomic scopes exists.
Regards,
Igor