The value of the setting 'CROWD background synchronization i

Error message

The value of the setting 'CROWD background synchronization interval' has changed from "${crowdSyncInterval.value}" to "${newCrowdDefault}". Please review your settings.

What it means

Companion of the LDAP warning in the same migration 295, this one covers CROWD_Sync_Interval. The old default was the free-text 'Every 60 mins'; the migration unconditionally rewrites the value to the new predefined 'every_1_hours' via updateAuditedBySystem({reason: 'Migration 295'}). The SystemLogger.warn fires only when the workspace had a non-default pre-upgrade value (crowdSyncInterval.value !== 'Every 60 mins'), i.e. a customized CROWD sync cadence is being replaced.

Source

Thrown at apps/meteor/server/startup/migrations/v295.ts:40

		// update setting values
		await updateAuditedBySystem({
			reason: 'Migration 295',
		})(Settings.updateValueById, 'LDAP_Background_Sync_Interval', newLdapDefault);
		await updateAuditedBySystem({
			reason: 'Migration 295',
		})(Settings.updateValueById, 'CROWD_Sync_Interval', newCrowdDefault);

		// notify user about the changes if the value was different from the default

		if (ldapSyncInterval && ldapSyncInterval.value !== oldLdapDefault) {
			SystemLogger.warn(
				`The value of the setting 'LDAP background synchronization interval' has changed from "${ldapSyncInterval.value}" to "${newLdapDefault}". Please review your settings.`,
			);
		}

		if (crowdSyncInterval && crowdSyncInterval.value !== oldCrowdDefault) {
			SystemLogger.warn(
				`The value of the setting 'CROWD background synchronization interval' has changed from "${crowdSyncInterval.value}" to "${newCrowdDefault}". Please review your settings.`,
			);
		}
	},
});

View on GitHub (pinned to b2c16d5842)

Solutions

After upgrade, review Admin -> CROWD and set 'CROWD background synchronization interval' to the cadence you want from the now-predefined options.
Pre-upgrade, record the current CROWD_Sync_Interval value (the warning also prints it) so you can restore intent.
Watch CROWD server load after upgrade — defaulting to hourly can hammer a previously 24h-synced directory.
Confirm via the audit log that the change was made by 'Migration 295', not by a user.

Example fix

// restore a slower cadence after migration 295
await Settings.updateValueById('CROWD_Sync_Interval', 'every_24_hours'); // pick a supported option

Defensive patterns

Strategy: validation

Validate before calling

// Pre-upgrade check for the CROWD companion setting
const crowd = await Settings.getValueById('CROWD_Sync_Interval');
if (crowd && crowd !== 'Every 60 mins') {
  console.log(`Custom CROWD interval "${crowd}" will be reset to every_1_hours by migration 295 — review after upgrade`);
}

Prevention

Record CROWD_Sync_Interval before upgrading; the migration forces hourly sync for everyone.
Check CROWD server load after upgrade since the default cadence is now hourly.
Restore the intended cadence from the predefined options immediately after the first post-upgrade startup.

When it happens

Trigger: Migration 295 executes during post-upgrade startup and the stored CROWD_Sync_Interval value is anything other than 'Every 60 mins' — for example 'Every 24 hours' or another custom string entered in the old field. The value is forced to 'every_1_hours' and the warning (old value -> new value) is logged once.

Common situations: Atlassian CROWD customers upgrading old Rocket.Chat installations where the sync interval had been tuned (typically slowed down to reduce load on the CROWD server). The migration normalizes cadence to hourly regardless of the previous setting, which can increase load on the CROWD server after upgrade.

Related errors

AI-assisted analysis of RocketChat/Rocket.Chat@b2c16d5842 (2026-08-18). Data as JSON: /api/errors/f58d29d6e179ba20. Report an issue: GitHub.