Member In Compliance State should not be logged as an error

Created on 23 September 2024, about 2 months ago

Problem/Motivation

We are experiencing a lot of logged "errors":

Detected "Member In Compliance State" subscribing {email} to list {list}. Trying again using double-opt in.

This happens under following circumstances:

MailChimp adds an email address to the ignore list if a member uses the link "unsubscribe from this list" in the email footer. This email address can't be resubscribed via API. You should see an error message if you try to add this contact using the "Email Newsletters" tool in the account tab Notifications. We can't influence this from the site. A member can resubscribe by clicking the button "Subscribe" in the email "You are now unsubscribed" that MailChimp sends after the contact is unsubscribed.

This is not really an error per definition, because the module tries to resolve the problem just after the log. This is triggering a lot of alerting in our monitoring which we cannot influence from our side.

It's similar to the issue in πŸ“Œ Should the message failed to signup because too many signups really be considered an error? Fixed .

Steps to reproduce

Proposed resolution

I propose to lower the logging severity to notice instead.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Active

Version

2.0

Component

Signup Module

Created by

πŸ‡©πŸ‡ͺGermany szeidler Berlin

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024