Flooded with Oban errors in Sentry since upgrading (see description for versions) about oban HOT 1 CLOSED

I'm sorry to hear your Sentry blew up.

since upgrading almost every error in sentry is related to Oban code I can look at but can't contribute to

All of those errors are coming from postgrex notification timeouts. Postgrex.SimpleConnection uses :gen_statem, and Oban uses SimpleConnection for PubSub notifications in many places, including plugins like Stager. For reference, the Postgres notifier is open source: https://github.com/sorentwo/oban/blob/main/lib/oban/notifiers/postgres.ex.

The issue here is with database timeouts and not with changes in Oban. Perhaps you have upgraded postgrex along with the other package upgrades, and the change to :gen_statem highlighted underlying timing issues?

Postgres is a decent default for PubSub, but it has drawbacks, including connectivity pressures, as you've discovered. Since you're on fly.io and likely distributed, I highly recommend switching to the PG notifier.

notifier: Oban.Notifiers.PG,

from oban.