Many thanks for the speedy help!

Cool! Thank you.

Thanks, @XenoRyet as long as setting MAXFAILEDATTEMPTS to 0 won't affect anything adversely (in terms of how or whether the recurring donations process), I'm for it. I'm not sure whether fr-tech or Evelyn would be better to reach out to PayPal if we go forward on this, maybe it could be driven by the level of tech talk involved?

One nice-to-have on a preferences page:

report all the dates in Hawaii time.

thanks, @XenoRyet

What would be helpful in terms of donor-facing messaging is anything we can do to prevent Paypal from sending messaging saying that we canceled the recurring donation. I am unsure about what modifying the number of retries really means, and whether there are adverse consequences to that. Is it possible that T230064: Investigate how to generate generic email for failed recurring donations will make this task unnecessary?

Sandra and I can use the report again, so I'm marking this Resolved as a one-off.

Some donors are reporting successful retries using Safari, so maybe this was a transient bug? Will continue to monitor for coming weeks.

Donor cid=36730826 got this login error today. They donated successfully INGENICO ID 000000657040025678570000100001, Ref 71463648.2 but also ended up as a result of some confusion making a duplicate donation as cid=36730790. We'll refund one of them and apologize for the error.

Thanks, I'll cc you on the email to spoof@

Thank you for following up with them @EMartin, it's disappointing that they're pushing this back onto the donors, but not entirely surprising.

Thank you, @TSkaff this looks great. I like the text, and the chronological list of contributions.

Sounds good to me.

Thank you!

Thanks for pushing PayPal, @EMartin

3 do nothing - the impact of this is probably fairly low & may become lower as the script runs

Here is a more recent example, ticket 640949 from 10/30:

Nope, thank you @Eileenmcnaughton - Resolving

Sure thing, and many thanks, this will improve a lot of different workflows!

Thanks for improving the error message, @Pcoombe I will check open tickets to see if we have any useful new feedback, but I don't think we have any console logs yet.

Solved in T231332: Unusable emails addresses

I am reopening this, as we've received new reports from donors about what sounds like the same issue. @EMartin would you let PayPal know that their report of the bug's demise was, as Twain would say, greatly exaggerated?

Thank you @Ejegg for confirming the accelerated time is not a problem. Good point on the Engage delay! I would bet that the majority of recurring card/paypal donors are not also sending checks, though there are always exceptions. Handling those exceptions manually is probably worth it, if we keep the larger group of recurring donors from having to ask us directly for their receipts.

Talking January scheduling at creative offsite (January TY email campaign, and such), it's emerging that the sooner we can send these annual summary emails the better. Could we get these all sent the first three days of January? @DStrine @Ejegg

Thanks, @Pcoombe we'll ask these donors for the usual extra technical details.

Thank you both!

@krobinson forwarded a good suggestion:

Yes thanks, it looks like everyone's able to do what they need.

That would be fantastic, @TSkaff. I do not know where the current TY email translations reside, but translators might be able to use them as starting points? If I can do anything to facilitate, please let me know.

@Ejegg Thank you! Beyond being tricky (impossible) to restart these, donors are very confused by PayPal's messaging.

Many thanks, @Pcoombe

Thanks, @mepps that cid says in Communication Preferences NO BULK EMAILS (User Opt Out) as Unchecked, but I also do see what you see, Opt-in=No in the Communication block.

Thanks @mepps CID 35666251 we did not update manually, I am pretty sure.

617549 is another example

Thank you. The other consideration is donor interest. The longer we push into January before sending these, the more I anticipate that DS will field 'where is my receipt' inquiry emails. In the interest of minimizing that, I would suggest accelerating the schedule, if possible.

One feature request: if the text of the Civi email template could contain a unique tag, it would help us to automate responding to any replies we receive in Zendesk. Something like CiviRec, would be great. Even better would be if the ISO code for language was appended, like CiviRecEN, CiviRecFR.

@Jgreen in email thread civi1001 mailq backup 9/18:

This again works for multiple DS agents, thanks so much @Eileenmcnaughton

Ok, she's able to use the search now, so I think this is all set. Thanks for the patches.

Just one followup:
-can we mark the new recurring instance in Civi contribution summary for DS and show the prior one as cancelled?

Hi all, @Jseddon is on leave, but this is on his agenda for when he returns. I know he's engaged with Shopify about this issue.

Thank you @Ejegg

Thank you @Eileenmcnaughton we were using it to find contacts for a single CID. This feature is really helpful when we're handling bulk email complaints, or unsubscribing deceased donors, or opting out check donors from paper receipts - useful in many cases! I will add any CIDs that are slow/hanging here.

Thank you @Eileenmcnaughton. The search by surname, firstname should find cid=35133991 which is the same donor. We tried every combination of search terms we could, with and without spaces. I will ask her to see if it's still not appearing in the results: if so, would clearing the browser cache possibly help?

@NNichols depending on what we cover in tomorrow's meeting with Sandra, I may close this task. Seems like the Deduper interface, older dedupe interface, and the script should all be aligned on this.

Thanks, @CCogdill_WMF I should have been clearer, I was thinking only of exact email address matches, but yes, let's cover this on Tuesday.

Multilingual support for this email would be super helpful, and directly increase the rate of donors re-upping. When DS follows up manually with those whose cards expired, we send this messaging, which we also have versions of in Dutch French German Italian Japanese Norwegian Polish Portuguese Romanian Spanish and Swedish.

Thanks, @Ejegg I was just thinking about asking you for more about what those options might mean when I saw David's invite for tomorrow - see you then!

Thank you @Ejegg This is worth fixing. We had a PayPal donor today say: "I did not finalize this payment! Please refund the $17.01. I did NOT complete the transaction. After investigation I decided not to donate and when directed back to finalize the transaction I did NOT authorize it." ZD 601194

Hurray! Thank you @MNoorWMF

Do we have any estimate of the timeframe for this resolving (before Monday's send?)?

Many thanks, @Pcoombe I nearly added you at the start but thought I'd let fr-tech sort as I wasn't sure who would be able to fix this. I will use the donate.wikimedia.org project for anything similar in the future.

Thank you, @CCogdill_WMF !

@Ejegg Kristie found another more recent example, from Aug 23rd: CID=5897344, PAYPAL_EC 31X68282EH588133Y and PAYPAL 31X68282EH588133Y

trying deploying DS Admin permissions to Seilo, ty @Eileenmcnaughton

Looks like these menus have synched up since Monday, they show the same # of queries in both places.

@CCogdill_WMF @spatton what do you think of this format:

So I was thinking the format could be like:

@DStrine If it makes sense for this task to supersede {T200529} I would be all for that! T200529 was partly a tool to enable manual followups, but automated followups are a great deal better.

Seilo cid=26034374 is also getting this error.

If this process could encompass PayPal as well as Ingenico that would be great. Also the question of whether these automated followups would happen in a monthly batch, or could be a more or less continuous process, is worth looking at in terms of debt to build and efficacy in terms of getting donors to re-up with us.

This would be a really helpful feature!

Thank you @Pcoombe