Hi @Vladi,
While Speckle supports doing ping pong 
between some apps, it wasn’t designed to work that way.
Where Speckle does a really good job is data extraction and specific A>B workflows (leaving aside the web collaboration & automate features for now).
In your proof of concept the problem is that when the beam is received in Revit 2025, it gets created with a new ID set by Revit. When you send this back into 2024, the IDs don’t match anymore and the update feature thinks it’s a new beam.
What you can do instead, is keep sending updates from 2024 into 2025, and the update functionality should keep working that way. Speckle doesn’t aim to keep track of elements and all their transofmations globally, we believe this is not very feasible nor the best aproach.
What specific workflow were you hoping Speckle could solve for you? Let me know if you have other questions!
PS
Welcome to the forum, feel free to Introduce yourself 
if you’d like!