We have identified the root cause and implemented a fix. However, this fix requires a long-running database migration that is already in progress and running smoothly.
Branch syncing is temporarily paused while the migration runs. No data will be lost, but new syncs will not start until the migration completes.
We apologize for the disruption and expect normal service to resume shortly. We'll post another update once the migration finishes and syncing is restored.