You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The membership site that I am dealing with has around 30 email lists and 10 membership levels because it has been around for a while. If a user has two memberships and they expire then the PmPro chron expire task takes care of unsubscribing the User.
However, if the Expire Memberships Chron job has more than a total of 2 memberships to expire then this integration produces Rate Limit API errors with the setup listed above. I had to implement my own error messaging in the Catch part of this integration to figure it out. From what I found, this integration loops through all the email lists in the system for some reason making API call(s) in order to unsubscribe a User.
It seems like this is rather inefficient. Perhaps a bulk unsubscribe endpoint would be good. Also, it would be nice if the "Catch" code was implemented by the plugin with a switch to show/log errors to stdout or a file. Now if we update the plugin my painstakingly written error catch code will be wiped out.
The text was updated successfully, but these errors were encountered:
The membership site that I am dealing with has around 30 email lists and 10 membership levels because it has been around for a while. If a user has two memberships and they expire then the PmPro chron expire task takes care of unsubscribing the User.
However, if the Expire Memberships Chron job has more than a total of 2 memberships to expire then this integration produces Rate Limit API errors with the setup listed above. I had to implement my own error messaging in the Catch part of this integration to figure it out. From what I found, this integration loops through all the email lists in the system for some reason making API call(s) in order to unsubscribe a User.
It seems like this is rather inefficient. Perhaps a bulk unsubscribe endpoint would be good. Also, it would be nice if the "Catch" code was implemented by the plugin with a switch to show/log errors to stdout or a file. Now if we update the plugin my painstakingly written error catch code will be wiped out.
The text was updated successfully, but these errors were encountered: