Sync stops working randomly and cannot be restarted without new sync chain. (Bookmarks no longer syncing, send to device no longer working reliably either.)

I wasn’t sure whether my desktop or laptop were most-used. Turns out to be pretty close. On my desktop, that code gave me 30995. On my personal laptop, 30850. On my work machine (another laptop), 23502. Looks like I should cut back on my casual surfing when I’m supposed to be working.

Edit to add: Updated my work laptop to the latest version, got 24747 this time with no other browsing activity in between.

1 Like

Hello, I’m new around here.

For about a month now, my devices (two PCs and a mobile) haven’t been syncing. I’m glad I found this thread at least; I was going crazy thinking it was just me. Device syncing seems fundamental in any browser, and it should be given the priority it deserves.
In my case, it’s true that I have a lot of bookmarks—I’ve been using them my whole life on Chrome, and I think I have around 10k. Anyway, until about a month ago, everything was fine; now there’s no way to fix this issue.

A question, if you don’t mind:

I’ve continued saving pages to bookmarks, even though they aren’t synced. If the bug were to be fixed now, would each device have its own bookmarks plus those from the other devices? Or how are these cases resolved? I use folders and bookmarks a lot for personal reasons, and I want to ensure I don’t lose anything.

Thank you very much, and I hope you find a solution soon.

Best regards.

EDIT:
I wrote the message days ago, but it has been published now. Just wanted to mention that the issue fixed itself (I didn’t touch anything, not even created a new thread). Regards!

1 Like

Be sure to back up and export your bookmarks manually! Mine got mixed up when I did a new sync chain on all my devices.

The best bet is to delete the sync chain and then uninstall brave on every device except the main/seed device that has the most up to date bookmarks. Start a new sync chain and add the “new” devices with the newly reinstalled clean versions of brave.

Have been plagued by this issue for a couple of months now. Last week sync suddenly started working again, but only for a few days and it is now showing the same TRANSIENT_ERROR as before. historyItems.length=41866 on my main PC. Apparently some items are still syncing properly (i.e. Search Engines) but Bookmarks and History are definitely not syncing and this is causing a major headache for me

My sync is failing again…
It’s been going well for a couple of weeks.

Every once in a while, I see the yellow non-working boxes on the sync internals page again… but just on the mobile browser. Once I exit Brave and open it again, it restarts and is green. (And works.) I’ll try to take a screen shot next time.

Unfortunately, the yellow boxes are here to stay again…

In my mobile browser, I see this:

I could resolve this in the last few weeks by closing Brave and restarting it. When I do it now, I get the green boxes flashing on the screen for less than a second like this:

… but it reverts to the yellow boxes almost immediately:

I’m seeing the same yellow boxes persistently on the desktop browser. So syncing no longer working on either…

Edit: I’m getting

    "error_message": "There are already 75000 non-deleted objects in store",
    "response_type": "OVER_QUOTA"

in brave://sync-internals/Traffic LogCommit Response

Anything I could do to resolve this?

2 Likes

Still down. I dont want delete the chain and create a new one if works only a few days. Need a solution :frowning:

1 Like

I had some issues few days back with the sync not working. But it was working again after a hour or so. I thought it was internet issue. But its seems otherwise.

1 Like

This problem was fixed for a good few weeks, but now back. Makes brave really unusable for me…

2 Likes

Just adding a +1 for me. Tabs from my Android device appear to have stopped syncing as of the past couple of days or so.

Highly reluctant to delete my Sync chain and start afresh if it doesn’t permanently resolve the issue.

1 Like

New chain, DISABLE HISTORY SYNC got it working at least for now
It sucks ik

1 Like

I thought it was a personal problem. But I realize that this is a problem that many people have.
I can’t sync my passwords anymore… it absolutely sucks.

2 Likes

@Alexey and @mattches I really would like to get some more momentum on this. Even with me, I’ve been getting error as below:

image

And everything has been backed off.

My devices have not been syncing with each other for over 21 days now.

Perhaps some of us experiencing different issues, but would be much appreciated if we can fix Sync for people where it’s not working. Not sure what all is needed to be provided.

3 Likes

@Alexey Any update/progress on this in the 2 months since your last comment in this thread? Happy to provide whatever information might be helpful.

1 Like

This is hurting my productivity at work and at home. Really hoping to have a resolution to this soon. Do we at least have a workaround?

2 Likes

@Saoiray
It looks like again a problem with reaching maximum number of server objects.
Normally the number of History objects at sync-internals table is 0, and the displayed objects number is the number of objects which failed to commit.
6240 means the server reached maximum limit and refuses to accept commits.

@ntarox
Prior to the first reports about the problem server objetcts limit was 50k and auto-expire period for history objects was 90 days.
Currently with https://github.com/brave/go-sync/pull/197 and https://github.com/brave/go-sync/pull/196 these numbers changed to 60 days and 75k objects.
By the feedback including this thread we can see that it gave some relief but not fixed the issue. The proper fix must be not just changing the limits, because with history sync it is easy to reach any. I switch to this task again, idea is to delete some amount of oldest history entries when server is about to reach the limit.

@CattleThunder

Do we at least have a workaround?

The only workaround is to recreate sync chain, re-join all devices and do not enable History sync type.

(May also help to turn off the History type and wait 60 days to allow auto-expire be triggered, but this workaround is not practical.)

1 Like

Okay, so is there a reason why we can’t/don’t have a warning appear that the average person could understand?

In all honesty, once it hit that limit, I should have received some notification or clear prompt to let me know things aren’t syncing. It shouldn’t only be randomly discovered when passwords, bookmarks, or whatever else suddenly isn’t visible.

The issue is it now tries to sync all history rather than just typed history, right? And I don’t see a toggle for that within Sync settings, which might be nice.

I also have to ask, why not have an option somewhere that allows us to manually delete things? Like if History has too many commits, why can’t I click to say to delete the earliest 1,000 or to delete History older than 60 days or something, which would then allow new to be made?

And I just tried manually deleting all history, which is said would delete history on all synced devices. But guessing that won’t really matter?

Are we assuming these two issues on Github may at least temporarily resolve our issues or will it continue to be frozen for us unless/until we create new sync chains?

1 Like

Last time the chain broke for me was Jan 27th, it died again today. So with the new limits it now breaks every ~2 months instead of every month - not really a solution.

Omitting history sync from the chain IMHO is not a solution either - this is core functionality for using a modern web browser on multiple devices and it has to work reliably.

In addition I very often (daily!) see “http error 504” on brave://sync-internals/
Just when recreating the new sync chain on my 5 devices today I had 504 errors on 3 of them, which takes even more time because I have to wait for them to expire (usually 1-2 minutes).

Screenshot 2024-03-20 at 16.43.46

@Saoiray

Okay, so is there a reason why we can’t/don’t have a warning appear that the average person could understand?

We should have it. The only reason why it wasn’t done from the beginning - it was expected to fix the issue in a fast way.

It shouldn’t only be randomly discovered when passwords, bookmarks, or whatever else suddenly isn’t visible.

Makes sense completely.

The issue is it now tries to sync all history rather than just typed history, right? And I don’t see a toggle for that within Sync settings, which might be nice.

Yes. This change was inherited from Chromium and the old code for typed url was removed completely in upstream. Back-port of any code including typed url sync is difficult and causes many conflict on each major update. And before all history sync we had behind the flag option to sync almost all history on a top of typed urls https://github.com/brave/brave-core/pull/16705 . So to use Chromium’s new datatype for sync all history seemed good idea.

I also have to ask, why not have an option somewhere that allows us to manually delete things?

For all other than History datatypes objects on server are deleted right after user deletes it in browser, like passwords or bookmarks. History entries are stored on the server in a different way. It is not implemented yet https://github.com/brave/go-sync/issues/178.

And I just tried manually deleting all history, which is said would delete history on all synced devices. But guessing that won’t really matter?

Yes, deleting of history happens by committing History Delete Directives. So if server reached 75k limit, it will refuse commit and other devices will not receive that and delete own history entries.

Are we assuming these two issues on GitHub may at least temporarily resolve our issues or will it continue to be frozen for us unless/until we create new sync chains?

These two PRs supposed to help, but they didn’t. There are users who reached increased 75k objects. If we will increase the limit again to for example 100k, - this will at least temporarily resolve our issues.

2 Likes