Forum Discussion

QuickbaseDevel1's avatar
QuickbaseDevel1
Qrew Trainee
2 months ago

Outlook Channel - Remote API returned authentication error 'refresh token'

For almost 2 years we have been sending emails without a problem and are using the Outlook channel in Quickbase Pipelines for this purposes. Since last week we have started to experience issues receiving following errors:

Remote API returned authentication error: (invalid_request) AADSTS900144: The request body must contain the following parameter: 'refresh_token'. Trace ID: 6f796e19-28f3-430c-8938-3a9274901800 Correlation ID: 3d7633a0-df23-404b-9b5a-d7df2400e3b6 Timestamp: 2024-09-30 18:38:43Z

We have not changed our Microsoft Azure AD account / application settings, this has just come out of nowhere. Using different email domains we experience the same issue. Is there anyone experiencing the same that can give us some guidance ? we have been looking to activate offline_access on the application in Azure AD, been review MFA settings, trying to use application passwords, etc. but to no good end result yet. And for almost a week now the Quickbase helpdesk is also not providing any active support. In the meantime we are reconnecting Outlook channels every hour to keep the lights on .... appreciate your input

Pipelines
  • QuickbaseDevel1's avatar
    QuickbaseDevel1
    Qrew Trainee
    2 months ago

    I can state our issue has been resolved last Friday. Whether it be by our only actions changing Microsoft and Sentra settings on offline access and application settings and/or with changes done by Quickbase. We have received little updates from the support team but would like toe believe Quickbase also made some changes.

  • AmandaThomas1's avatar
    AmandaThomas1
    Qrew Trainee
    2 months ago

    Hi @QuickbaseDevel1!

    I've been receiving this error for a few weeks now. Support let me know that it should be resolved with October's update, but that went live last weekend and I still am receiving this error.

    Do you recall which specific settings you changed in the Microsoft account that you use for your Outlook channel? I reopened the ticket on Monday but haven't received a response, so I'm hoping your insights might help.

    Thanks!

    • QuickbaseDevel1's avatar
      QuickbaseDevel1
      Qrew Trainee
      2 months ago

      Hi Amanda, the most important change we made was to ensure the application in Azure AD has the necessary permissions, including "offline_access," which allows the app to use refresh tokens. However, that by itself did not resolve the issue immediately. We also disconnected and re-installed the Outlook channel connections in Quickbase, resulting in us having to go into each pipeline using Outlook emails to select the new installed Outlook channel connection again. That together with whatever Quickbase changed on their end (they provided no details to me if and if so what they had changed) led us to be able to get it working again. Since we have not experienced any issues anymore (fingers crossed).

  • AmandaThomas1's avatar
    AmandaThomas1
    Qrew Trainee
    2 months ago

    Thanks!

    I was actually just able to get this working again by simply reauthorizing the token (again).