Apply look-back reconciliation window to Chuffed campaigns #4

New issue

Closed

opened 2026-01-27 01:20:23 +01:00 by blacklight · 0 comments

blacklight commented

2026-01-27 01:20:23 +01:00

Owner

Chuffed's transaction acknowledgment is flawed, and it often displays donations on a campaign page even before a confirmation from the circuit.

When the transaction fails, it often takes a few minutes for Chuffed to remove the record from their database.

If the glitch happens while the scraper is running, then those transactions will counted.

Once removed, the next iteration will process records from the latest cursor, so it'll miss that some of the previous records have been removed.

The issue is definitely on the callback implementation on Chuffed, but it's starting to become common enough that it needs to be tackled.

For Chuffed each round of scraping should also perform an additional call that looks backwards from the latest cursor with a reasonable window (10-20 transactions), and reconcile any transactions that have been removed by also removing them from the local db.

Chuffed's transaction acknowledgment is flawed, and it often displays donations on a campaign page even before a confirmation from the circuit. When the transaction fails, it often takes a few minutes for Chuffed to remove the record from their database. If the glitch happens while the scraper is running, then those transactions will counted. Once removed, the next iteration will process records from the latest cursor, so it'll miss that some of the previous records have been removed. The issue is definitely on the callback implementation on Chuffed, but it's starting to become common enough that it needs to be tackled. For Chuffed each round of scraping should also perform an additional call that looks backwards from the latest cursor with a reasonable window (10-20 transactions), and reconcile any transactions that have been removed by also removing them from the local db.