Major Headache due to Sync issues, passwords now incorrect!

@TWSkip: Thanks for reaching out. I’m sorry for the trouble you've been having with Dropbox sync! Just to clarify, all 1Password vaults sync'd with Dropbox are local vaults, as they're not part of a 1Password.com account. There isn't really anything we can do to help directly as sync (and conflict resolution) is handled by Dropbox entirely in this case — and frankly I'm not too surprised that Dropbox is having trouble sorting out conflicts given that the data you're trying to merge has diverged over a long period of time. What I can do is give you a few suggestions that you can use to get back on track:

1. DON'T delete stuff and merge stuff without backing up your data first, and having a solid plan. I'm hopeful that you haven't destroyed anything important, but that isn't clear from your comments. If you have, the only possible solution would be to try to restore files from the Dropbox website, and that can be a bit of a nightmare.
2. Determine if you have a full set of good data anywhere. I really don't have any kind of sense of that, or how many vaults are involved here exactly, but the most important thing is that you have your data somewhere. Syncing it other places can be sorted out later.
3. If you do have a known-good copy of your data (restored from a backup?), save backups of everything else on other devices and then reset 1Password on those.
4. Setup each device from scratch using Dropbox to sync the known-good vault(s) everywhere needed. Then you'll have the same data everywhere, and Dropbox can incrementally sync changes between all devices.
5. Ensure that Dropbox is setup properly going forward. This is an ongoing process: Dropbox sync will be disabled if the app is out of date, if the account or data is unavailable, and in other error states. It's necessary to keep the client up to data (and 1Password, in the case of mobile devices, since it has to update to Dropbox's latest APIs just as their own client does).

That will get you back up and running, and maintaining your sync setup going forward. However, you may want to consider a 1Password.com membership, since it gives you access to all of the apps, the web interface, and does away with license management and sync configuration altogether — you simply login to your account to authorize a device and access your data:

1Password.com

You can try it for free for 30 days to take advantage of all of its benefits](https://support.1password.com/why-account/). And honestly 1Password Families has made sharing data securely with my loved ones much easier than it was when I was using Dropbox for everything too. I don't miss having to troubleshoot that stuff or configure syncing for each individual vault across many devices.

Either way, I hope this helps. Be sure to let me know if you have any other questions! :)

@TWSkip: That doesn't sound like a bug at all. You're merging long-diverged datasets. But regardless, this isn't something 1Password handles; it just gets the data from Dropbox, which is doing all of the syncing and conflict resolution. 1Password literally just reads the data from disk. Did you try my suggestion? That will get you back to a stable state, since you won't have multiple devices all trying to push different data to the Dropbox server.

@TWSkip: It's definitely confusing. I understand it, but it's difficult to articulate. I think your example may help though, if I'm understanding you correctly. You're talking about a specific item in the Trash with a certain password. To you, it appears that it is not in your vault, but that's not the case: "Trash" is essentially just a flag — metadata for an item; to Dropbox and 1Password, this is just a single file on disk with data stored in it. Put a different way, regardless of whether it is Trashed, what the password is, etc., Dropbox is just syncing bits in a file, and 1Password is reading it. So if it's "Trashed" in the vault on one device and "in the vault" on another (it's technically always part of that vault, unless you move it to another vault and/or empty the Trash, but that's a bit of a digression about encryption and data formats), to Dropbox it's just the same file slightly changed, and to 1Password it's the same item just with different metadata.

I know Kate means well here, and her pedigree as a tester is unimpeachable, but I'd really suggest trying what I suggested earlier. We could potentially gain a lot scientifically from following her advice, but I suspect you just want things back to normal.

It doesn't happen often, but I have enough experience with Dropbox, both personally and helping others, to have a pretty good sense of what's going on here, and to give a rather extreme example that was so hilarious for me that I am still kicking myself for not recording a video. Essentially, when I got myself into a similar predicament in the past, I could effectively see in real time my devices and Dropbox having what I would call the technological equivalent of young siblings fighting in the back of the car over a toy: "It's my turn! Mommm!" I had desktop notifications on my Mac when the Dropbox client would sync data to the server, and the server would immediately sync its data back — just an endless cascade of "X was updated" notifications, which would probably have continued for all eternity (it went on for at least an hour before I put a stop to it), had I not disabled Dropbox sync, Trashed the vault, and just let the server sync a fresh copy of what it was intent on giving me.

Anyway, not particularly useful in the way of advice, but hopefully this example gives you a bit of insight into what we're dealing with here — and why we decided to create our own sync mechanism tailored to fit 1Password. Nothing against Dropbox. They do a phenomenal job within the constraints of filesystem-based syncing. It's amazing that it works at all, and as well as it does. As a nerd, I can appreciate and admire that. But most people don't want to nerd-out over sync technologies — or configure sync for each vault individually across multiple devices — they use want their data to be available everywhere, so we purpose-built 1Password.com to do that seamlessly. Cheers! :)