RocketChat/Rocket.Chat · warning

The value of the setting 'LDAP background synchronization in

Error message

The value of the setting 'LDAP background synchronization interval' has changed from "${ldapSyncInterval.value}" to "${newLdapDefault}". Please review your settings.

What it means

Logged by database migration 295 ('Change old LDAP_Background_Sync_Interval ... to pre-defined values') during server startup on first boot after upgrade. The setting changed from free-text (old default 'Every 24 hours') to a select with fixed options; the migration unconditionally writes 'every_24_hours' via updateAuditedBySystem, and warns only when the workspace had a NON-default value (ldapSyncInterval.value !== 'Every 24 hours'), because that custom interval is being silently discarded.

Source

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

		const newCrowdDefault = 'every_1_hours';

		const ldapSyncInterval = await Settings.findOneById<Pick<ISetting, 'value'>>('LDAP_Background_Sync_Interval', {
			projection: { value: 1 },
		});
		const crowdSyncInterval = await Settings.findOneById<Pick<ISetting, 'value'>>('CROWD_Sync_Interval', { projection: { value: 1 } });

		// 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

1. After upgrading, open Admin -> LDAP -> Background Sync and set 'LDAP background synchronization interval' back to the cadence you need (the new select offers predefined options such as every hour).
2. Pre-upgrade: note your current interval value so you know what to restore; the warning message itself prints the old value.
3. If you run CROWD too, check the companion CROWD_Sync_Interval warning — the same migration changed it.
4. Verify the audited change log shows 'Migration 295' as the actor for the update, so you can distinguish migration changes from manual ones.

Example fix

// after migration 295 reset your cadence (server-side example)
await Settings.updateValueById('LDAP_Background_Sync_Interval', 'every_1_hours'); // pick a supported option
// available options follow the pattern 'every_N_hours' / 'every_24_hours'

// Pre-upgrade check: will migration 295 discard my custom LDAP interval?
const current = await Settings.getValueById('LDAP_Background_Sync_Interval');
if (current && current !== 'Every 24 hours') {
  console.log(`Custom interval "${current}" will be reset to every_24_hours by migration 295 — re-set it after upgrade`);
}

When it happens

Trigger: Migration 295 runs (version bump from a release older than it). The pre-upgrade read of LDAP_Background_Sync_Interval returns a document whose value is anything other than 'Every 24 hours' — e.g. 'Every 1 hours', 'Every 12 hours', or custom text typed into the old free-text field. The value is overwritten with 'every_24_hours' and the warning, containing the old and new values, is printed once.

Common situations: Upgrading a workspace where admins had tuned LDAP background sync to run hourly or every few hours to keep external-directory users in sync faster; admins who typed arbitrary strings into the old free-text interval field. After the migration, sync frequency silently becomes once a day, which can surprise large organizations relying on frequent sync.

Related errors

• The value of the setting 'CROWD background synchronization i
• The default value of the setting 'Login Terms' has changed t
• The default value of the setting has changed. Please review
• The default value of the custom setting has changed. Please
• LDAP_disabled

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