-
Notifications
You must be signed in to change notification settings - Fork 310
run Gratipay 118 #2729
Comments
Reviewed 31 accounts. |
Backup taken and verified. |
Droplet spun up and updated. |
Script started. |
|
Any help with this, @balanced? |
Mail sent to support@balancedpayments.com:
|
Sounds from support convo w/ @msherry that this may be an issue on Balanced's side. The successful debit against the hold was in an inconsistent state (no logs or events in the dashboard, and not listed under payments on the customer page). @msherry reconciled it to a failed state so now we have the hold for the user and two failed debits against it. |
Since we crashed while the mega-transaction was open, we are likely to hit #2663 again. |
|
Let's drop the outer cursor for now, it's only an extra protection, it's not actually needed.
|
Hot fix edited. |
Rerunning ... |
Script ran for 19 minutes (0:19:26.089372). |
What's our check for #2663? |
#2663 checked. Only one user affected, and the amount involved is pennies. Safely skipping. |
Log downloaded and droplet destroyed. |
MassPay is off. Gonna bisect to find the record with the wrong fee cap. |
Found it. |
MassPay done and posted back for 63 users. |
Escrow shuffled. I moved $50,000 to cold storage today (first time in a while since I hadn't checked in on New Alliance for a while). |
Stats for the Gratipay team: receiving amount is up by 5.3%, number of tippers is up by 13.8%. |
😊 |
117
The text was updated successfully, but these errors were encountered: