Why Sequence Settings Sometimes Fail to Save

Last updated: December 16, 2025

When working in the Sequence Builder, you may occasionally see an error saying “Failed to save sequence settings.” This is usually caused by a few common scenarios and does not necessarily indicate that your sequence is broken. Below are the most frequent reasons this error appears and how to resolve them.

1. Multiple Users Editing the Same Sequence

If two people are editing the same sequence at the same time, one user’s changes can overwrite or conflict with the other’s. When this happens, Unify may block the save to prevent inconsistent or corrupted configurations.

How to fix:

  • Confirm no one else is editing the sequence.

  • Try saving again after a moment.

2. Temporary Sequencer or Server Hiccups

Occasionally, the backend sequencer service can experience a brief delay or timeout.
Even if your sequence is valid, the save request may fail while the system is catching up.

How to fix:

  • Wait 30–60 seconds and try again.

  • Refresh the page if the issue persists.

3. Missing or Invalid Variables

If any step includes a variable that is empty, incorrectly formatted, or no longer exists, the system may block the save to prevent sending broken messages.

Common examples include:

  • A variable pulled from a field that is no longer part of the Audience

  • A typo in a variable name

  • A variable placed in a step where it’s not supported

How to fix:

  • Review all email and task steps for highlighted or missing variables.

  • Remove or correct the invalid variable.

4. Browser or Connection Issues

Local issues such as a dropped network connection, expired session, or cached builder state can prevent the save from completing.

How to fix:

  • Refresh the page

  • Try saving again

  • Clear browser cache if the issue repeats

  • Switch to another browser or Incognito mode

When to Contact Support

If you continue seeing the error after checking the items above, there may be a deeper configuration issue. Please send:

  • A link to the sequence

  • A screenshot of the error

  • The step you were editing when it occurred

Our team will investigate and help you resolve it quickly.