Same here, I did get it to reauthorise but now the rules are erroring ‘Provide a valid email’ which it clearly is a valid email! Hope it fixes soon!
I have had the exact same issue since yesterday! Mine started a couple of weeks ago, I managed to fix it but it has started again. I have a ticket raised and they are having me check all sorts but if we have all been having this issue at the exact same time then surely its something global for Asana to resolve?
We have now been able to re-authenticate the connection.
I escalated this issue internally yesterday and received confirmation of a major outage affecting the Outlook integration.
We have now been informed that the issue has been fixed.
Apologies for the inconvenience caused, and thank you for your patience.
@Irish_Makimura I am still having the same issue. We have multiple rules and the errors showing are ‘Refresh auth token’ and ‘User authentication not found’. When clicking ‘connect to Outlook Email’ it opens the browser window to authenticate but nothing else happens. I don’t even have the ‘if nothing happens click here’ option we usually get
Thank you for your patience while we looked into this.
Our support team confirmed that this issue is related to broken Outlook authorization objects, and in some cases manual intervention may be required on our side to fully clear them. They are still investigating what that process will involve and how long it may take.
In the meantime, here are two workarounds that may help unblock you:
Option 1 (Recommended for immediate workaround):
Create a new Outlook email action in your rule and copy over the existing configuration. This often restores functionality without waiting for the backend fix.
Option 2:
Try resetting the Outlook authorization by following these steps:
-
Go to App settings in Asana
-
Deauthorize Outlook Mail
-
Return to your Rules
-
Open the affected rule and re-authenticate Outlook
Deauthorizing Outlook will clear the broken authorization object and may resolve the issue.
We appreciate your patience while this is being investigated, and we apologize again for the inconvenience caused.
Out of curiosity, if Asana has confirmed this as a major outage, why hasn’t it been reflected on their status page? This should affect the SLA uptime, but there is nothing reflecting this outage.
Same issue, tried re-setting outlook authorization which didn’t work.