Make > Monday Requests Failing

[JayRenn]

This morning, I started receiving warnings that ALL of my scenarios have been paused. If I resolve the incomplete executions, within 1 minute, a new set of incomplete executions arise. The complete error shown in Make is included below.

Looking for a solution online tells me that Monday’s 2023-10 API is supposed to go into effect today or tomorrow.

Is there anything we need to do in Make or Monday to get the requests working again?

{
   "message": "Field 'items_page_by_column_values' doesn't exist on type 'Query'",
   "locations": [
      {
         "line": 1,
         "column": 2
      }
   ],
   "path": [
      "query",
      "items_page_by_column_values"
   ],
   "extensions": {
      "code": "undefinedField",
      "typeName": "Query",
      "fieldName": "items_page_by_column_values"
   }
}

Thanks,
Jay Rennemeyer

[samliew]

Everyone is experiencing this issue suddenly due to changes on Monday’s end. Please try to search before posting, and avoid creating new threads for the same issue as it fragments the discussion.

• Problem with Monday.com modules changing to new API version
• Monday.com Field 'items_*anything' doesn't exist as of about 3 hours ago
• Monday.com "Get Items" List Board's Item" Modules Blocked Due to Nov 2023-10
• Monday integration with error "The operation failed with an error. [200]"
• Make > Monday Requests Failing

Also, for quicker assistance with bugs and technical problems, you may want to contact support directly. The more users contact support, the more likely it will get prioritised.

See the main thread below:

Problem with Monday.com modules changing to new API version

I’m hoping this is a very temporary issue, and I doubt anyone at Make will see this in time to make any difference, but it’s worth a try… With the Monday.com API changing to the new version today (Jan 15), the modules on my existing scenarios are not adding the version into the header, despite using the new version code. I created a new scenario and added the same module and it does include the version in the header. Existing scenario with error: [image] [image] New scenario works fine: …

[Michaela]

Hello @JayRenn

Thank you very much for flagging this here in the community.

Our development team is investigating this issue with the highest priority. Although a solution hasn’t been found yet, I’m closing this thread so that we can all communicate in one place. That’s also where I’ll be posting updates.

(Also, special thanks to @samliew for sharing the main thread here )

I sincerely apologize for any frustration, trouble, and inconvenience this has caused you.
Thank you very much for your patience and understanding.

[Msquare_Automation]

Hi @JayRenn

It is better to replace native modules with GraphQL query for board search and Get an Item.

We have just completed the update a few minutes back.

MSquare Support
Visit us here
Youtube Channel