I suspect you’re hitting the same “feature” we did, where another service/host is requesting a new Server-to-Server OAuth token and invalidating the one you are using in this particular instance:
I suspect you’re hitting the same “feature” we did, where another service/host is requesting a new Server-to-Server OAuth token and invalidating the one you are using in this particular instance: