@BenLee is right, the added row will only be synced back during the next sync. And even if you manually force the sync right away, it may still not pick up the new row because there’s no guarantee that the row has been already saved to the doc snapshot or not.
However, there is one thing that you can do (albeit in a hacky fashion). You can add an action after your Crossdoc::AddRow that will trigger the sync, without having to wait for under 1 hour or asking the user to sync the table themselves. Because it’s dependent on Automation bot and works with a delay, this could actually be sufficient to wait until that added row is actually already in the snapshot. You can give it a try and tell me if that works: