21-May-2026 — Email routing: Refresh works, and failures stop hiding #252

build 653 — commit 5f27414

A set of fixes so the Email Routing Log and mail forwarding tell you the truth when something goes wrong.

The Refresh button now shows new mail

On the Email Routing Log, the Refresh button used to keep the same time window it had when you first opened the screen, so any mail that arrived since then never appeared. Only a full page reload would bring it in. Refresh now moves the window up to the current moment and shows the latest messages. If you have set your own date range, that is left untouched.

You cannot deploy mail forwarding without the credentials it needs

Deploying or updating the Brevo re-send forwarding worker without Mail API credentials used to produce something that could never work. The deploy button is now disabled until those credentials are set, with a message pointing you to Mail Settings > Mail API Settings.

Failed deliveries no longer report as success

A forwarding failure could previously be logged as "success, 0 errors" even though the mail was never delivered. Now a real failure is recorded as an error, the sending mail server holds onto the message and retries it (so it is not lost while you fix the settings), and the Email Routing Log marks the message with a red badge reading "Worker invocation failed for this message... mail to this address will not have been delivered".

Workers that are already deployed keep their old behaviour until you redeploy them, which the screen prompts you to do when it spots they are out of date.