You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Missing Postgres implementation: The if ($isPostgres) {} block is empty. The Postgres branch never assigns the query, so performUserSync throws an exception on every Postgres cron tick. The exception is caught upstream but recordSyncTime() is never reached, so the "last sync" timestamp is never updated.
PHP operator in SQL: Line 506 contains o.username !== '' (PHP not-identical operator) inside a raw SQL string. The database receives an invalid expression and rejects the query.
Scenario:
On any Postgres installation the scheduled user sync silently fails every cron cycle. Admins see a stale "last sync" timestamp and no error message because the exception is swallowed.
Suggested fix:
Implement the Postgres branch using o.users::jsonb @> to_jsonb(o.username) or equivalent.
Severity: HIGH
Location:
lib/Service/OrganizationSyncService.phplines 478–531Description:
The user-sync query has two defects:
Missing Postgres implementation: The
if ($isPostgres) {}block is empty. The Postgres branch never assigns the query, soperformUserSyncthrows an exception on every Postgres cron tick. The exception is caught upstream butrecordSyncTime()is never reached, so the "last sync" timestamp is never updated.PHP operator in SQL: Line 506 contains
o.username !== ''(PHP not-identical operator) inside a raw SQL string. The database receives an invalid expression and rejects the query.Scenario:
On any Postgres installation the scheduled user sync silently fails every cron cycle. Admins see a stale "last sync" timestamp and no error message because the exception is swallowed.
Suggested fix:
o.users::jsonb @> to_jsonb(o.username)or equivalent.!==with<>in the SQL string.Source: deep team-reviewer pass 2026-05-27