While our team works as hard as possible to make sure that you never encounter an issue on the monday.com platform, we have a few tips to help as quickly as possible if you do. Let's take a look! 🙌

 

How does it work?

When you encounter an issue with the monday.com platform, we encourage you to fist try our initial steps for troubleshooting, and if those are unsuccessful, reach out to us! Once you reach out to us, your report is passed to the developers who specialize in the area where you're experiencing the issue. They'll use the details you send to us to investigate the issue, locate it, and correct it. When the issue is fixed, we'll reach out to you to make sure everything is working as expected.

 

There are three categories of issues -- the first is called a "board issue", the second is called an "automation issue", and the third is called an "integration issue". Here are quick descriptions of each so you can jump ahead to figure out what you need to include in your report for a speedy resolution:

 

Reporting board issues

What should I include when reaching out to you?

To help us serve you best, there are a few pieces of information that our team needs to know to understand and provide guidance with efficiency and effectiveness.

1. A detailed description of the issue, including the intended behavior and the unexpected behavior you observed.
2. List the exact steps you took. If it suits you, you can send us a screen recording that captures the issue and the steps taken leading up to it. Knowing your pathway in executing an action within monday.com is helpful for us to not only understand but to test on our end, recreate the issue, and work towards a solution.
   • • This video is a great example of how to record and dictate the exact steps taken.
3. The time and date that you first saw this issue occur. Having this point of reference allows us to drill into specific events in a long log of events associated with your account.
4. Scope of the issue. If possible, it would help to know how many members of your team are also experiencing this issue. Do other members of your team see the same behavior that you're seeing? Or does this seem to be only happening for you?
5. Relevant permissions.
   • • Who is the board owner or the doc owner? And the workspace owner?
     • What is the board, dashboard, or workdoc type? Shareable, Private, or Main?
6. Include the board ID, item ID, automation or integration ID, dashboard ID, or monday workdoc ID. You only need to include the ID for the feature that is This can be found by simply copying the URL from your browser. Here's a guide on accessing these IDs: Board, item, column, and automation or integration IDs
7. Screenshot of the developer console. This does not need to include any information from your board. To learn how to screenshot your console, follow the steps in this article: How to Open the Developer Console. It is important to first open the console, then complete the same steps that produced the unexpected behavior, and then take a screenshot.

 

Reporting automation issues

What should I include when reaching out to you?

The following may seem like a lot of information, but our team will need all of it to investigate the issue. Otherwise, it's almost like chasing a ghost! 👻 If you send over all of the following information when you contact us, we'll be able to solve the issue quickly.

1. The recipe of the automation. The recipe might be as simple as "When Status changes to Done, move item"
   • Please tell us the whole automation, no matter how long. We need to know each block used to help.
2. The automation ID. After turning on developer mode, this ID can be found in the lower right corner of the automation recipe. Here's a guide on accessing the automation ID: Board, item, column, and automation or integration IDs
3. The item ID and board ID. If the issue is related to the automation not completing the intended action, it would be beneficial to know details about the item where the automation failed. We do not need this information if the error occurred while setting up the integration. This is a guide on locating the IDs: Board, item, column, and automation or integration IDs
4. The trigger ID. This is more specific than just the automation ID.
   • What is the trigger ID? Each time an automation is triggered, the instance that the automation was triggered is assigned a specific ID. Our team can use this ID to search our logs for the specific time that the automation failed.
   • How can I find the trigger ID?
     • 1. Go to the automations activity log.
     • 2. The fourth column in the activity log is the "Trigger ID".
     • 3. Click where it says "Copy ID" to copy the ID! 
     • 
5. Time. The date, time, and time zone the automation was triggered.
6. Email address. The email address of the individual who triggered the automation.
7. Other helpful pieces!
   • Does the issue happen on multiple boards?
   • Does the issue occur if you delete and set up the the automation again?
   • Does it fail or give an unintended result every time or only sometimes?
   • Did it work previously and now it doesn't? If yes, when did it last work as expected?

 

Reporting integration issues

What should I include when reaching out to you?

1. The recipe. If possible, send a screenshot. If you can't, type out the recipe you set up and indicate if it is a recipe you selected from our Workflows center or a custom automation.
2. The integration ID. After turning on developer mode, this ID can be found in the lower right corner of the integration recipe. Here's a guide on accessing the integration ID: Board, item, column, and automation or integration IDs
3. The item and board ID numbers. If the integration is not completed as intended, we will also need details about the item where the action failed. We do not need this information if the error occurred while setting up the integration. This is a guide on locating the IDs: Board, item, column, and automation or integration IDs
4. Time. The date, time, and time zone the automation was triggered.
5. Email address. The email address of the individual who triggered the automation.

 

That's it! Once you let us know about your issue, we'll get on the case. 🕵️ 

 

 

If you have any questions, please reach out to our team right here. We’re available 24/7 and happy to help.