# Is there a way to test Livesync / websockets is working

**URL:** https://vaultwarden.discourse.group/t/is-there-a-way-to-test-livesync-websockets-is-working/1435
**Category:** Help
**Created:** [February 6, 2022, 4:07pm UTC](https://vaultwarden.discourse.group/t/is-there-a-way-to-test-livesync-websockets-is-working/1435 "2022-02-06T16:07:07Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![jjlin](https://avatars.discourse-cdn.com/v4/letter/j/e19adc/32.png) [@jjlin](https://vaultwarden.discourse.group/u/jjlin)
#### Post date: [February 6, 2022, 7:10pm UTC](https://vaultwarden.discourse.group/t/is-there-a-way-to-test-livesync-websockets-is-working/1435/2 "2022-02-06T19:10:53Z")

</div>

> [@Need explaining websocket and push notifications](https://vaultwarden.discourse.group/t/need-explaining-websocket-and-push-notifications/87/2):
>
> Bitwarden currently doesn’t have a concept of data conflicts or versioning of an entry as a whole (i.e., not just password history). So for example, if you make a change in the browser extension (say, change the password) and then make another change in the mobile app (say, add a URL), then your password change would be lost because the mobile app (when used with bitwarden\_rs) wouldn’t have gotten a notification to reload the updated entry. On the other hand, if you made the change in the mobile…

---

_[View the full topic](https://vaultwarden.discourse.group/t/is-there-a-way-to-test-livesync-websockets-is-working/1435)._