-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validate 202404 Chase prime txns #149
Comments
katefike
changed the title
Backfill 202404 transaction emails into the MX
Validate 202404 txns
Jun 18, 2024
Moving mbox
|
katefike
changed the title
Validate 202404 Chase txns
Validate 202404 Chase txns and add Chase accounts
Jun 18, 2024
katefike
changed the title
Validate 202404 Chase txns and add Chase accounts
Validate 202404 Chase txns
Jun 18, 2024
Identical txns
Two different Huntington Uber withdrawals - one at 02:43:02, one at 03:17:1
Identical Chase SAVE A LOT withdrawals - both for 7:06 PM
email IDs 2023 and 2018 are also from Uber, so they're probably distinct txns... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps
Local Testing
export ISDEV=True && python3 -m sage
and verify the emails can be parsedvalidator/real_data/Chase_visa-prime_220618-240618.csv
python3 -m validator Chase_visa-prime_220618-240618.csv 4-2024
Detour
Create a retry mechanism for unparsed emails. ✔
DONE WHEN
The text was updated successfully, but these errors were encountered: