The question none of those three has answered, asked on 4, 9 and 11 September:
Does attempting or completing a new consent revoke or rotate the refresh token an application already holds?
This is the whole problem. Existing token refreshes keep working, as Harvey_W also observed, so integrations already connected are running normally. But that means the only way to find out whether the fault has cleared is to attempt the broken flow, and if that attempt kills the working token, the recovery path is the same broken flow. Nobody is going to test under those conditions.
So the situation is that a fault nobody can confirm is fixed sits behind a test nobody can safely run. That is not a degraded feature. For any integration that loses its grant for any reason right now - expiry, revocation, a transient error, a new environment - it is a total outage with no manual workaround.
What I am asking for, in priority order:
A written answer on whether a new consent attempt affects an existing refresh token. Yes or no. This does not depend on diagnosing the 504.
The refresh token lifetime. Asked 26 August, still outstanding.
Confirmation of whether it is currently fixed, so somebody can test it deliberately rather than by accident.
Harvey_W , if you get an answer on any of these before I do, please post it here. And if anyone else is hitting this, say so in this thread - it is clearly counting.
I have a hard migration deadline of 15 October and I am currently unable to authorise the new environment or test a single MYOB workflow in it. I will keep providing logs, headers, cf-ids and timestamps to anyone who asks. What I cannot do is keep waiting without knowing whether anyone is looking at it.
OAuth in my side seems working normally now. But I'm not sure how this got fixed. The only change I've made was that I removed one redirect URI in mymyob's developer dashboard.
And my scopes setting: offline_access, openid, sme-company-file, sme-contacts-customer, sme-general-ledger, sme-inventory, sme-sales
