text change

deploy/catcrafts-credits.timer

@@ -1,23 +1,26 @@
-# Every five minutes. Two things set the floor and the ceiling:
+# Hourly, because this is now the BACKSTOP rather than the primary path.
 #
-#   * bunq rate-limits reads to roughly 3 GET per 3 seconds per method, so one
-#     call per five minutes is nowhere near it. The cost of going faster is
-#     nothing technical; it is just noise.
-#   * a donor watching the order page wants confirmation while they still care.
-#     Five minutes here plus the reconciler's own 60 s cadence means a fresh
-#     order confirms within about six minutes of the money landing.
+# Since the bunq webhook landed, a payment normally settles within seconds: bunq
+# pushes it, the handler writes the credit, the reconciler picks it up. This
+# timer exists for the case the webhook cannot cover — bunq retries a callback
+# roughly six times over a few minutes and then DROPS IT FOREVER, so a payment
+# that arrives while the backend is restarting (every deploy is a restart) is
+# lost to the webhook with no error anywhere. An hourly pull turns that from a
+# silently missing donation into an hour of delay.
+#
+# It was five minutes while the pull WAS the settlement path. Hourly is the
+# right cadence for a safety net, and it keeps the noise down.
 #
 # Persistent=true so a laptop that was asleep pulls once on waking instead of
-# silently skipping every window it missed — which is exactly when a donation
-# would otherwise sit unacknowledged overnight.
+# silently skipping every window it missed.
 [Unit]
-Description=Pull bunq credits for catcrafts.net every 5 minutes
+Description=Backstop pull of bunq credits for catcrafts.net (hourly)
 
 [Timer]
 OnBootSec=2min
-OnUnitActiveSec=5min
+OnUnitActiveSec=1h
 Persistent=true
-AccuracySec=30s
+AccuracySec=5min
 
 [Install]
 WantedBy=timers.target