David Simpson Apps
Products • Microsoft 365 SharePoint integration for monday.com • Documentation
Docs • Troubleshooting

Missing credentials

Ongoing monday.com incident Since 2026-06-10 Acknowledged by monday.com

This behaviour is caused by a bug in the underlying monday.com automation engine which has been acknowledged by monday.com.

It is not caused by third-party app developers such as ourselves.

If an automation or workflow has failed, you may have seen the following error message:

monday.com is failing to correctly send credentials.

Follow the steps at https://credentials.m365.app/

What's happening here?

Automations can fail for a number of reasons, but when the above error message is sent by the automation block, this is because monday.com's own system for issuing Microsoft 365 login credentials (OAuth) is not working correctly.

Please note that the Microsoft 365 integration app is working completely as intended, but monday.com itself is behaving incorrectly.

When an automation block runs, our app asks monday.com to provide a fresh set of credentials to access Microsoft 365. monday.com handles this process entirely behind the scenes, so our app never sees your actual Microsoft 365 login — only a short-lived access token that monday.com generates on our behalf.

If monday.com fails to correctly hand our app a valid access token for Microsoft 365, the above error message is displayed, and the automation block fails.

What to do next?

Things you can do yourself

Having noticed that a small number of our customers continue to have this problem, monday.com support responded with the following workaround:

  1. Re-select and re-save credentials

    1. Find the original owner of the automation/workflow
    2. Get them to open and edit the automation block again.
    3. Re-select the credentials from the credentials dropdown
    4. Save the automation/workflow
    5. Trigger the automation/workflow again.

    monday.com support says:

    If a user who is not the original credential owner opens and saves an automation, the automation/workflow builder can sometimes drop the credential reference upon saving.

    Having the original credential owner re-open the workflow block, re-select the credential from the dropdown, and save the automation should restore the payload binding.

  2. Re-authenticate the connection

    If the previous step did not work:

    1. Open and edit the automation block again.
    2. Connect to Microsoft 365 again and reauthorise the account with Microsoft 365
    3. Save the automation/workflow
    4. Trigger the automation/workflow again.

    monday.com support says:

    Re-connecting or re-authorising the account credential directly within the automation block forces a fresh token binding (userCredentialsId) across the serialisation chain (BlockCredentialsGeneratorService)

    This is their naming of their own processes in their backend system.

  3. Recreate from the automation or workflow from scratch

    If the previous steps did not work, you should attempt to recreate the automation or workflow completely from scratch. This should fix any problems caused by bugs in monday.com's backend infrastructure.

    monday.com support says:

    Create a fresh automation block directly from scratch, rather than duplicating an existing one or using a template. This forces a clean serialization binding on our end.

    This "serialization binding" is the same process in monday.com's backend system which they mentioned in the previous step.

Contact monday.com support

If the problem affects you, contact support@monday.com so that they are aware of the bug in their automation engine. Every account that submits a support ticket adds more weight to the evidence needed to get this problem solved.

To speed up resolution of your support ticket with monday.com support, please:

  1. Provide a link to this page for context
  2. Grant remote support access: How to grant remote support access
  3. Provide board and automation/workflow links
    • For the board, this should look similar to https://youraccount.monday.com/boards/12345678 where youraccount is your account name & 12345678 is the board ID.
    • For workflows, this should look similar to https://youraccount.monday.com/custom_objects/12345678 where youraccount is your account name & 12345678 is the workflow entity ID of the workflow.
    • For automations, browse to the automation & click on the "Info" tab to find the workflow entity ID of the automation
  4. Request they add support@dsapps.dev to the ticket
    • This allows us to follow along with the request and supply any additional information they may need
Missing the first 3 steps above will result in delay, and follow-up requests from monday.com support.

Technical details (for monday.com support)

This section is included to help monday.com support to understand the problem that is occuring.

During normal times, the automation block expects monday.com to POST a payload to the app which is in the following shape:

{
  "payload": {
    "credentialsValues": {
      "microsoftToken": {
        "userCredentialsId": 1231,
        "accessToken": "..."
      }
    }
  }
}

We use the accessToken part of this, which is supplied by monday.com to connect to the Microsoft Graph APIs on the user’s behalf.

When this problem occurs, the payload is in a different shape, and looks more similar to this:

{
  "payload": {
    "credentialsValues": {}
  }
}

The access token required to connect to Microsoft 365 is missing from the payload, so the connection with Microsoft 365 cannot be made.

In order for this automation block to work as normal, the monday.com infrastrcuture must be fixed to provide a correctly shaped payload to this app.