Monday.com Field 'items_*anything' doesn't exist as of about 3 hours ago

[Jessica_Gwynne]

Happy Monday morning - all of our automations are broken!

It seems something has happened with the Monday.com API, and now any Make module that relates to an item, is failig with runtime error 200 (see below.). This is one of many (about 70 on my company and the same again on a friends).

This is a new module I added, to see if the modules had changed/been updated and I just needed to refresh them all, but it seems more in depth than that.

I have no idea where to start to troubleshoot this, there is nothing on the Monday.com side only an API update that’s not due until tomorrow.

Can anyone point me in the right direction, please?

Thankyou!

To get helpful responses

• explain your goal with as much context as possible
• mention any steps you’ve tried so far

Include screenshots of

• your scenario setup (functions, mappings, variables, etc.)
• module configurations and outputs
• any error messages you are getting

[Cyclo_Group]

Hey Jessica, there are a few other users with this issue. Jump over here https://community.make.com/t/problem-with-monday-com-modules-changing-to-new-api-version/24153

What country are you in? Its already the 15th where I am.

[Jessica_Gwynne]

Thankyou - Australia, so the 15th already too! I’ll checkout the other thread.

[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: …

[MondayExpert]

Hi all,

I am also still experiencing this issue on one of the standard Monday modules within Make.

[samliew]

@MondayExpert

I am also still experiencing this issue on one of the standard Monday modules within Make.

Yes, this is a known issue that everyone is facing at the moment. See the main discussion thread linked above.

[Michaela]

Hello @Jessica_Gwynne

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 @Cyclo_Group and @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 @Jessica_Gwynne @MondayExpert

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