Sync in OnePassword is designed to be invisible: you save a login on one device and it appears on the others within seconds. When that stops happening, the symptom is always the same — an item that exists somewhere but not everywhere — while the cause sits in one of a few well-defined places: the sign-in state of the app, the sharing settings of the vault, the network the device sits on, or the version of the app itself.
Before changing anything, answer two questions: does the missing item exist on the device where it was created, and do other items sync normally on the device that looks out of date? The answers split the problem cleanly in half — one broken item versus one broken device — and the fixes are completely different.
Confirm the device is actually signed in
The most common cause is also the most overlooked. An app that was signed out — by a password change, a manual sign-out, or a subscription hiccup — keeps showing cached data while syncing nothing. Open the app's account settings and check the sign-in status before anything else. If a re-authentication is needed, after a fresh one password login on that device the vault usually updates within a minute.
Watch for the subtler version of this problem: a device signed in to a different account than you think. Families and teams frequently run personal and work accounts side by side, and a phone quietly signed in to the older account will never receive items saved to the newer one.
Check whether the vault is shared with that device
Not every vault follows you everywhere, and that is by design. If an item lives in a vault that was never shared with a family member or teammate, their device will sync perfectly — just without that vault. Open the item in question, note which vault it belongs to, and confirm that every person and device expected to see it actually has access. In team accounts, an administrator can check and adjust vault permissions in a few clicks.
This also explains the "I saved it on my work account" pattern, where an item created while signed in to one account simply does not belong to the other. Moving it between vaults solves the mystery instantly.
Rule out the network in front of you
Sync requires a working connection to OnePassword's servers, and some networks make that harder than others. Corporate firewalls, hotel captive portals, and parental-control filters can block or delay the connection without producing a clear error. If a device syncs on mobile data but not on office Wi-Fi, the network is the variable — try a different connection, complete any portal login, and let the app retry on its own.
Power-saving modes deserve a mention too. Aggressive battery savers on phones and laptops can suspend background sync for hours, so a device that "never updates" until you open the app is often simply being efficient, not broken. Whitelisting the app in your device's battery settings restores background updates.
Update the app and check the clock
Mixing app versions across devices is a slow-motion support burden. An outdated build may keep working for months and then fail quietly after a server-side change, so keep every device on the current release from the official store. While you are there, confirm that the device's date and time are set automatically; a clock that drifts far enough can break the secure connection sync depends on.
As a final step, a manual refresh from the app's menu forces an immediate check instead of waiting for the next scheduled one. If that returns the missing item, the sync engine was healthy all along — it simply had not been asked.
When the problem is bigger than one device
If nothing syncs anywhere, and every device shows the same stale state, the issue is likely account-wide: an expired subscription, a locked account, or a service incident. Check the vendor's status page and your billing details, then contact OnePassword's official support if the account itself looks wrong. We are an independent fan site, so we cannot inspect accounts or trigger a resync — but with the checks above, you will already know exactly which layer failed before you open a ticket.