Monday integration broke as soon as I upgraded to the paid plan

Features
,
1

The strangest thing happened. I created my beautiful scenario, tested over many days, launched to the team to start to use, then I upgraded to the PAID plan. As soon as I upgraded, the monday scenario that creates the items can no longer connect to the board and I get this error: Function ‘buildArrayOfParametersToChangeColumnValues’ finished with error! getLinkedItemBoardId is not defined

I have re authenticated, removed the connection and re-added, recreated the module and nothing works. This is so frustrating as it had been launched to the team and as soon as I start paying Monday, I cant use it ahhhhh

Any ideas?

6 Likes
3

It isn’t anything you have done, I’m getting the same error too

You’ll need to raise a support ticket with Make, so they can diagnose if the problem is on their side or at Monday (too which they should then communicate to their contacts at monday to resolve)

4

@Libbie Same here exactly, only in my case, I moved the board to a new workspace.

I’m raising a ticket on both platforms just to be sure, and I will update with any changes.

** At least for me, the affected scenario can still run properly, I just can’t access the module’s settings and edit the columns

1 Like
5

Glad to ready I am not the only one experiencing this. The first time in history I didn’t break anything myself :grinning_face:

I didn’t change anything on my scenarios like you guys btw. I just popped up.

6

Same, no change on my side either, integration just broke down. probably a change in Monday…

7

Hello @here :waving_hand:

Thank you for bringing this to the community!

We’ve escalated the issue to our development team, and they’re working on it as a priority. We’ll keep you updated as soon as there’s any progress. In the meantime, if you have any further questions, open a support ticket at make.com/ticket.

We sincerely apologize for the inconvenience and truly appreciate your patience and understanding. :folded_hands:

2 Likes
8

Encountered this error for the first time and I do not know how to troubleshoot it. Function ‘buildArrayOfParametersToChangeColumnValues’ finished with error! getLinkedItemBoardId is not defined

9

Same issue here, getting the same error when I try and use update items modules. :worried:

10

Same issue, any update?

11

its happend to me also, any update?

12

Hi Misha, do you have an update on this issue?

13

Just adding that I’m also having this issue. I did place a ticket as well…hoping for resolution soon.

14

+1 also having this issue :folded_hands:

15

Not sure this helps…I’m seeing this same error (last 24 hours) using the monday ‘create an item’ module. I can recreate the error by creating a quick scenario…if I use the module to create in a board with with connected columns or mirrored columns the error appears…deleting the mirrored or connected columns in the board the error does not appear. Again this was not the case about 24 hours ago.

16

Any updates on this? We are waiting for this issue now to be resolved to get the integration deployed to production.

17

Did you get any updates on the ticket? I also submitted one yesterday but no updates just yet.

18

From my ticket update last night… “reported this issue to our devs and currently being checked”.

1 Like
19

Im getting the same error and Ive been on the Enterprise plan for a while.
As a work round I allow the module to create the item and then use a update column value of a specific item module to update the required fields.

20

I got a quick “reported this issue to our devs and currently being checked” response to my ticket as well but still waiting for anything further. It’s affecting a few mission critical Scenarios, that I don’t have time to rebuild with the above workaround, so hopefully they’ll be a fix soon.

3 Likes
21

Hi Misha, would be amazing to get an update if possible? If we could get an indication of whether it is a major issue that is explected to take another week or so, if its nearly solved or if its likely not to be solved. Just so we can plan around and look at other solutions.

1 Like