Skip to Content

Flyer reminders retried after our failures, honest password-reset errors, and cleaner logs

Shipped 2026-10-27

Flyer reminders

The flyer currency job recorded the “last month” and “last week” reminders as sent before sending them, so a member whose email failed never got that reminder. It is now recorded once the email is accepted, or once it fails in a way a retry can’t fix (bounced, unsubscribed, invalid, no address). A failure on our side, such as Mandrill being down, leaves it for the next run. Deactivation is unchanged and never waits on the email.

Password reset

When the reset itself failed (for example a database error), the error was logged as a Redis token problem and the member was told their passcode was invalid. It now surfaces as password_reset.failed with a plain 500, and the response no longer includes the raw error, which for a database error included the SQL.

Logs

  • Ask Rusty questions are no longer written to the request log, and saved questions no longer appear in query spans.

  • Positional SQL parameters are logged by shape for strings (free text, addresses, IPs); numbers and nulls stay visible.

  • passcodeOption (email / sms) is no longer redacted.

  • Push events are push.sent and push.no_tokens instead of sentences.

  • Each rejected Accordion record logs accordion.record_rejected with its ids and reason.

  • Jira: TUN-908 

  • PR: #1019 

  • Author: @alexhobday

Last updated on