Fixed by upgrading New Relic to 8.5.0! Other environments had this upgraded, but not the failing one.
On Fri, Sep 1, 2023 at 5:26 PM Torsten Krah <[email protected]> wrote: > Am Freitag, dem 01.09.2023 um 15:18 +1000 schrieb Tim N: > > We're seeing this too, but not in all our environments. We also use > > NewRelic. > > Does it happen without NewRelic too? If not, better ask NewRelic about > that problem. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
