Opera Workspaces sync limits when tab counts grow across devices

Goal

I want to rely on Opera's Workspaces feature to keep three distinct tab groups (roughly 40–60 tabs total) consistent between a desktop and a laptop, both signed into the same Opera account. The documented behavior is that workspace names and tab state synchronize across devices when account sync is enabled.

Constraints and uncertainty

Opera is Chromium-based, and sync engines typically impose per-item or per-datatype limits on how many entities propagate. It is unclear whether Opera documents a maximum number of tabs per workspace, a total tab ceiling for sync, or whether large workspaces silently degrade (partial tab lists, stale ordering, lagging updates) rather than failing visibly.

There is also a related uncertainty around session persistence: if the browser is closed before workspace state is committed to the local profile, some tabs may not be restorable, which would compound any sync gaps on the second device. Assume a current stable Opera release on desktop; exact behavior may vary by version and should be verified against release notes.

Questions

1. Is there a documented or observable limit on how many tabs per workspace Opera sync will propagate between devices?
2. When a workspace exceeds that limit, does sync fail silently, truncate the tab list, or surface an error?
3. Does the Tab Saver hibernation of inactive workspace tabs affect whether those tabs are included in sync at all?