:PROPERTIES:
:ID:       9d000aeb-ab38-4d68-b8ac-7407b16be41b
:END:
#+title: 2022-04-22

* Fixing restored deleted subscribers
- *What was broken?* :: Restored subscribers remained marked as deleted within the recipient service, causing automations to fail
- *When was it broken?* :: This issue has likely existed since we introduced the
  deleted status in Recipient ([[https://gitlab.aweber.io/CP/Services/recipient/-/commit/ead64b148475088addbf727af49d0bb318fe3a05][ead64b14]]).
- *What did you do to fix the problem?* :: Using a script
  (https://gitlab.aweber.io/correlr/restore-subscribers), I iterated through all
  of the subscribers on the affected accounts, correcting their subscriber
  records in recipient if they were found to be in this state.
- *How many customers did it likely impact?* :: Any customer that has had
  deleted subscribers restored via the Admin interface since 2017.
- *Is the issue automatically fixed for all customers now?* :: Because there is
  no way to identify customers for which deleted subscribers have been restored,
  only the customers noted in this ticket have been fixed. Other customers that
  are identified as being affected by this issue will require the same manual
  intervention.
- *Does the customer or CS need to manually do something to fix their account?* :: No,
  the data for the customers noted in this ticket has been corrected.
- *Should a new monitoring check, metric, or test be created to prevent this from happening again?* :: Efforts
  are underway to migrate the recipient service away from its current subscriber
  data store ([[https://jira.aweber.io/browse/CCPANEL-12001][CCPANEL-12001]]). Once that is done, it will no longer be possible
  for subscribers to continue to get into this state.