I guess what happen is that the client has already read the second party before you saved the first one. And the client keep it when you switch to the next record. This is the expected behavior from the client, this allows to have fast UI response and minimize the load on the server-side.
Now it would possible to define an on_write method to force to reload the target parties.
But it will probably better to work on Replace on_write with bus message