Thank you for reporting this issue.

How long did you wait before you decided to change something to trigger sync?

Hello there 

I waited about half an hour and then  I have triggered the sync with the creation of a bookmark.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Actually, from the description of this specific feature, cloud sync should indeed be disabled.

If you enable this setting, the settings stored in Google Chrome profiles like bookmarks, autofill data, passwords, etc. will also be written to a file stored in the Roaming user profile folder or a location specified by the Administrator through the Google Chrome policy. Enabling this policy disables cloud sync.

Hello 

Yes, the GPO disables the cloud sync feature (we dont need this).
My problem is that the settings which were saved in the roaming profile were not synced on the startup from Google chrome.
That means when I work on client 1 (Create some Bookmarks in Chrome etc) and then login to client 2 and start chrome I don't see the newly created bookmarks. On the sync-internals page I see that the profile didn't sync. After the creation of a new bookmark, chrome will sync the settings and I can see all bookmarks.  

Deleted: Sync_Chrome.PNG 121 KB

	Sync_Chrome.PNG 121 KB View Download

+Julian

Julian, would you have an idea how this is supposed to behave?

Hi Julian,

Could you please have a look?

YEs I have this bug on my radar and will look into it as soon as I undig myself from the pile of stuff on top of me right now :)

Indeed we are aware that in some cases the sync process is delayed until there is a changed entry to be synced to the shared state. It seems to be happening if the browser is too busy with other stuff during startup. I will try to force sync update as soon as the browser is idle and operational rather then until the first change happens as it is now.

CL in review here https://chromium-review.googlesource.com/c/chromium/src/+/951771

Triage ping: Any updates on this?

Mikel proposed a different way to achieve this that should be cleaner but I haven't had chance to look into that yet. I hope to be able to revisit later this quarter.

Triage ping^2: Any updates?

Triage ping^3: Greetings from the next quarter! ;) Any updates here?

sync-triage ping^4: any updates?

sync-triage-ping, any updates?

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1fac2bcb83a6898e81f4845cf634f132f855bc23

commit 1fac2bcb83a6898e81f4845cf634f132f855bc23
Author: Julian Pastarmov <pastarmovj@chromium.org>
Date: Mon Sep 10 14:43:07 2018

[sync] Add an immediate refresh trigger for local sync upon sync startup.

Otherwise no sync happens on browser startup and changes made on other
computers only become visible after some syncable event is committed to the
sync local backend.

BUG= 816379 

Change-Id: I60c0fc8e67edd104fdc1a636abad2e829baf4f99
Reviewed-on: https://chromium-review.googlesource.com/1209622
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Commit-Queue: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589907}
[modify] https://crrev.com/1fac2bcb83a6898e81f4845cf634f132f855bc23/components/browser_sync/profile_sync_service.cc