Configuration change is not applied

Use this guide when you saved settings but scheduling, generation, or publishing still follows the old behavior.

Symptoms

You may see one or more of these signs:

• Cadence windows, CTA mode, learning settings, or platform capabilities behave as they did before you saved.
• The config form shows your new value in the effective summary, but the next post or generation run ignores it.
• Submit appeared to succeed, yet App Home or a dependent workflow still uses old windows or defaults.
• A validation error blocked save, but you retried without fixing the field Slack flagged.

Config changes flow through the settings config forms workflow. Successful saves should appear in audit history and refresh App Home or close the modal depending on context.

Likely causes

• You saved at the wrong scope. Brand saves do not change org defaults for other brands. Org saves do not remove existing brand overrides.
• A more specific scope override still controls the field you care about. Account, platform, pillar, campaign, and brand layers can each win over a parent default.
• The change has not propagated yet. Effective config can take a short time to reach dependent workflows.
• The submit failed on invalid YAML, JSON, window times, or required fields, but the modal closed before you read the errors.
• Arrays at a child scope replaced a list entirely while you expected items to merge.

Review Configuration inheritance before you stack multiple overrides. Object fields merge by property. Arrays replace entirely when you save a new list.

Checks

1. Open /social, choose Settings, and reopen the same config domain and scope you edited (org, brand, campaign, pillar, platform, or account).
2. Read the effective summary shown in the form. Compare it to what you intended to save.
3. Note the scope label on the form title. Confirm it matches the brand, campaign, or account you are testing.
4. Check whether a parent or child scope still shows a conflicting value for the same field.
5. If submit returned field errors, reopen the form and read each message before you change values again.

Fixes

Confirm scope and inheritance

1. Save at the narrowest scope that should control the behavior you are testing.
2. Remove or update child overrides when a parent save should apply everywhere below that scope.
3. Re-read the effective summary after each save.

Wait for propagation

1. Allow up to five minutes after a successful save before you retest dependent workflows.
2. Close and reopen App Home, or rerun the workflow that depends on the config, after the wait.
3. Schedule a test post, run generation with learning enabled, or publish to a gated platform to confirm behavior.

Fix validation errors on resubmit

1. Reopen the config form if submit returned field errors.
2. Correct invalid YAML, JSON, window times, or required fields shown in the modal.
3. Submit again. Do not retry with the same invalid value.

Confirm the fix

The effective summary matches what you saved. The next workflow run reflects the new windows, CTA mode, platform capability, or learning setting. Audit history shows the save at the scope you chose.

Prevent it next time

• Pick the correct scope before you edit. Use Configuration inheritance as a reference when you add overrides.
• Save once, wait five minutes, then test with a fresh post or generation run instead of retesting immediately.
• Read validation errors on the first failed submit instead of closing the modal.
• Document which scope owns each override when several teams edit the same brand.

Contact support

Escalate when the form shows the new value in the effective summary but behavior stays wrong after five minutes across a fresh test post.

Send support:

• Workspace name
• Brand name
• Config domain (for example cadence, CTA, learning)
• Scope you edited (org, brand, campaign, pillar, platform, or account)
• Approximate save time
• What you expected versus what the test post did

Related articles:

• Edit configuration forms
• Configuration inheritance