@KHancock99 and Yamini noted from Zendesk ticket #1314116 that a donation manually settled on May 25th has not reached Civi yet.
The transaction ID is 177088652.1 and PSP ref is R6DGT369H3PNT872
I spot-checked some other recent manual settles and they've all reached Civi quickly:
| 175893257.1 | settled 5/9 | civi 5/9 |
| 175887749.1 | settled 5/8 | civi 5/9 |
| 177083754.1 | settled 5/24 | civi 5/24 |
Would it be possible to re-run the audit for May 25th?
Hi @MBeat33 something odd happened here. I'll get it into civi manually so we can get them a TY email and then look into the actual issue.
I created them in civi:
cid=59717237
I manually added them and the donation so the TY email didn't autosend.
The issue here is this donation never had a row saved for it in contribution_tracking. So when the audit tried to import it it errored and skipped over this donation:
civicrm.wmf.ERROR: adyen_audit: MISSING_MANDATORY_DATA No contribution tracking data retrieved for transaction
@Ejegg mentioned that the lack of data in contribution tracking could be due to a deadlock from the backfill of the new contribution tracking table. I looked into the timeframe there weren't any deadlocks around when this donation was made. In the logs I checked the run before and the run where this donation would have been they both ran normally with no errors:
contribution_tracking_queue_consume-20230525-072502.log.civi1001.bz2 right before it would have been consumed
contribution_tracking_queue_consume-20230525-072701.log.civi1001.bz2 has 651 and 653 but not the 652
@MBeat33 I made a task for the issue that caused this donation to not get imported T339182: Audit: create missing contribution_tracking entries instead of skipping importing them. Is it alright if I resolve this one since we manually added the donor and donation to civi to get them their ty email?