Reliable until it’s not…

There’s literally no fallback anywhere on a plugin/service which is designed purely for sending reliability. Not the first time we’ve ended up with timeout errors due to API faults, which this time funnily enough coincided with the issues that on the Status page on 2nd December were only reported as being related to the SMTP service and latency only. The plugin doesn’t re-attempt if it’s timed out either.

There’s literally no consideration by the plugin devs anywhere for fallback/warnings if the connectivity with the API fails for a message – why is there no fallback if any kind of error occurs? Simple SMTP settings or a slack notification/webhook – literally anything to warn that a message has failed to send to the API. Come on guys, not difficult and really lets things down.