I've reproduced this issue and it definitely appears to be a bug with the OpenAPI resource connector, in particular, as the refresh flow reliably triggers on a similarly configured REST API resource. I also confirmed that the refresh flow always triggers after a failed query run, so you can think of the below dropdown as defining an additional trigger.
I've documented the issue internally and will follow up here as soon as I have news to share. While not ideal, refactoring this as a REST API resource should be a functional workaround. Let me know if you have any questions and I look forward to seeing you in Office Hours going forward!
That's super helpful Darren. Thank you for the follow up and validation of the issue. Also for confirming the behaviour of refresh auth triggers, as that was unclear to me.
Unfortunately there's no scenario I'll refactor this as a REST API. It's just so much additional work compared to using openapi spec to autogenerate endpoints. I'll be eagerly awaiting word from you on this