When multiple Team Members are working on the same Blast, there is a risk that overwriting each other's work - for this reason, we primarily recommend coordinating not working on the Blast at the same time.
Even the best coordinated teams may find there are times when this happens by accident. To help protect your team's work, save and work conflict notifications will help your team understand when more than one session of a single Blast is actively being edited and saved.
Working Conflict
Working Conflicts occur when an Auto-Save, Save as Draft, or Rescheduling is triggered with at least two active sessions of a Blast. This can occur when two people are working on a Blast at one time, or if you have the same Blast opened in multiple windows or tabs.
For example:
Person 1 and Person 2 have a drafted Blast open. Person 1 makes a change and saves successfully. Person 2 makes a change and attempts to save, but instead, they see a warning.
When you click Save as Draft, a Working Conflict notification will appear, with an option to Save & Overwrite or Return to Editor, and not save your work.
Overwriting will not change what the other user in this Blast is currently seeing; however, if they try to make edits and save after you, they will then see this warning.
If you have Autosave on, you will first see this error whenever an automatic save is attempted:
Click View Details to see the conflict details window above.
💡 Don't want to Overwrite, but also don't want to lose your work?
Temporarily Save as Template.
In the Blast editor, click the ⋮ ellipsis menu button, then click Save as Template. Exit, then go to Blast > Templates to find the new Template.
State Conflict
State Conflicts occur when an attempt to change the state of a Blast is made when at least two active sessions of a Blast are open.
This can occur when one of the sessions attempts to:
Schedule or Send Now a Drafted Blast
Save as Draft a Scheduled Blast
Send now on a Schedule Blast.
Overwriting will not change what the other user in this Blast is currently seeing; however, if they try to make edits and save after you, they will then see this warning.
If you have Autosave on, you will first see this error whenever an automatic save is attempted:
Click View Details to see the conflict details window above.
State Conflict - Sending or Sent
Another type of State Conflict exists for a Blast which has entered a sending or sent status while another active session tries to make changes.
When trying to Save as Draft, a State Conflict window will explain that the Blast is already being or has sent, when this occurred, and by what team member.
After a Blast has entered sending or sent state, it is not possible to Save & Overwrite it, so only the Return to Editor option is available.
💡 Unable to Overwrite, but also don't want to lose your work?
Send a Sample or Temporarily Save as Template.
In the Blast editor, click Send Sample to send a copy of the Blast to your inbox for you to copy and paste from in a new Drafted Blast.
Or, from the ⋮ ellipsis menu button, click Save as Template. Exit, then go to Blast > Templates to find the new Template.
If you have Autosave on, you will first see this error whenever an automatic save is attempted:
Click View Details to see the conflict details window above.
If you have any questions at all, please don't hesitate to reach out to us at support@cerkl.com or use the support Chat toward the bottom right-hand corner of any cerkl.com page.