The default value of the setting has changed. Please review

Error message

The default value of the setting has changed. Please review your settings.

What it means

Logged by migration 317 ('Change default color of OAuth login services buttons'). Rocket.Chat moved from blue (#1d74f5 / #0082c9) filled buttons to a neutral gray style: new background #e4e7ea, new label #1f2329. For the four built-in background keys and four label keys in settingsToUpdate (SAML_Custom_Default_button_color, CAS_button_color, Accounts_OAuth_Nextcloud_button_color, Accounts_OAuth_Dolphin_button_color, and their *_label_color counterparts), the migration checks getSettingValue(key): if the value still equals the OLD default, it warns (including key and newValue) and updates the DB value to the new default. Customized values are left alone.

Source

Thrown at apps/meteor/server/startup/migrations/v317.ts:73

		await LoginServiceConfiguration.createOrUpdateService(serviceKey, data);
	}
}

addMigration({
	version: 317,
	name: 'Change default color of OAuth login services buttons',
	async up() {
		// TODO: audit
		const promises = settingsToUpdate
			.map(async ({ key, defaultValue, newValue }) => {
				const oldSettingValue = await getSettingValue(key);

				if (!oldSettingValue || oldSettingValue !== defaultValue) {
					return;
				}

				SystemLogger.warn({ msg: 'The default value of the setting has changed. Please review your settings.', key, newValue });

				return Settings.updateOne({ _id: key }, { $set: { value: newValue } });
			})
			.filter(isTruthy);

		await Promise.all(promises);

		const customOAuthButtonColors = await Settings.find({
			_id: { $regex: /^Accounts_OAuth_Custom-[a-zA-Z0-9_-]+-button_color$/ },
		}).toArray();
		const customOAuthButtonLabelColors = await Settings.find({
			_id: { $regex: /^Accounts_OAuth_Custom-[a-zA-Z0-9_-]+-button_label_color$/ },
		}).toArray();

		const buttonColorPromises = customOAuthButtonColors
			.map(({ _id, value, packageValue }) => {
				if (packageValue !== value) {
					return;

View on GitHub (pinned to b2c16d5842)

Solutions

No action required if the new gray look is acceptable — this is an intentional design change.
To restore the old blue, set the affected *_button_color / *_button_label_color settings back (e.g. #1d74f5 background, #ffffff label) in Admin -> Login options.
To keep custom branding permanently, set explicit values BEFORE upgrading — the migration only rewrites settings still equal to the old defaults.
Then call updateOAuthServices() (or restart) so login service configurations reflect the new colors.

Example fix

// restore pre-317 blue button after the migration
await Settings.updateOne({ _id: 'CAS_button_color' }, { $set: { value: '#1d74f5' } });
await Settings.updateOne({ _id: 'CAS_button_label_color' }, { $set: { value: '#ffffff' } });

Defensive patterns

Strategy: validation

Validate before calling

// Pre-upgrade: find built-in button settings still at old defaults (migration will recolor them)
const watched = [
  ['SAML_Custom_Default_button_color', '#1d74f5'],
  ['CAS_button_color', '#1d74f5'],
  ['Accounts_OAuth_Nextcloud_button_color', '#0082c9'],
  ['Accounts_OAuth_Dolphin_button_color', '#1d74f5'],
  ['SAML_Custom_Default_button_label_color', '#1d74f5'],
  ['CAS_button_label_color', '#1d74f5'],
  ['Accounts_OAuth_Nextcloud_button_label_color', '#0082c9'],
  ['Accounts_OAuth_Dolphin_button_label_color', '#1d74f5'],
];
for (const [key, oldDefault] of watched) {
  if ((await Settings.getValueById(key)) === oldDefault) {
    console.log(`${key} is at old default and will be changed by migration 317`);
  }
}

Prevention

Set explicit brand colors for every login button setting you care about BEFORE upgrading — migration 317 only rewrites values still equal to the old defaults.
After upgrade, visually check the login page; the new defaults are a gray background (#e4e7ea) with label #1f2329.
Keep a documented list of theme-related setting ids per provider so redesigns are easy to audit.

When it happens

Trigger: Migration 317 runs on startup after upgrading from a pre-317-version release, and for one of the eight listed keys the current value equals the old default ('#1d74f5' or '#0082c9'). Each such key produces one warning and one Settings.updateOne({$set: {value: newValue}}).

Common situations: Any workspace upgrading across the release that introduced the neutral login-button redesign while never having customized CAS/SAML/Nextcloud/Dolphin button colors. Admins notice login buttons turned gray after upgrade; the warning is purely informational and cosmetic — no functionality breaks.

Related errors

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