Summary:

On Tuesday August 6th, 2024, starting at approximately 8:24 PM PT, we received user reports that when creating content using a template that includes an assigned email alias that differs from the default, the email alias reverted to a default alias for the program when attempting to save. It was identified that the email alias error was caused by a regression introduced by a bug fix where a restricted user could potentially publish as an unassigned email alias. A hotfix was deployed to rollback this change which resolved the issue.

Impact: 

The scope of this incident affected users who attempted to create and send campaigns between 08.06.2024 8:24 PM PT and 08.07.2024 12:31 PM PT. Impacted users experienced upon selecting an email alias within a campaign, and attempting to save, the email alias reverted to the default if re-opened instead of applying the selected alias. Users additionally could not update or save a draft to fix, this caused campaign delays and prevented impacted users from sending time-sensitive communication from the appropriate alias.

Root Cause: 

The root cause was identified as a regression introduced during the latest deployment of a hotfix to address potential restricted users who publish as an unassigned email alias when using a template. The scoping of the original bug fix was too restrictive, resulting in the inability of any users regardless of permission level to be able to override the default alias in campaign drafts.

Mitigation:

Once the root cause was identified a revert of the deployed hotfix that caused the email alias error was mitigated, restoring functionality by 08.07.2024 12:31 PM PT.

Recurrence Prevention:

A fix will be deployed on the original software change done for the noted bug where a restricted user could potentially publish as an unassigned email alias. Firstup will explicitly test to be certain that author aliases can be set on new drafts and are not overridden by the default alias and will add this to all future regression tests.