Skip to main content

I have an automation that’s running through Make.com. It makes an API call back to Monday to update multiple column values. The code is stable and no changes have been made. All of a sudden today I’m getting this error:


400] 0{“message”:“parsing error: syntax error: unexpected line terminator”,“locations”:{“line”:5,“column”:16}],“extensions”:{“code”:“PARSING_ERROR”}},{“message”:“parsing error: syntax error: expected a valid Value”,“locations”:r{“line”:8,“column”:3}],“extensions”:{“code”:“PARSING_ERROR”}}]


Here’s the query:

mutation {

change_multiple_column_values (

item_id: <>,

board_id: <>,

column_values: “{

"text__1" : "18, 19, 20, 21, 22, 23, 18, 19, 20, 21, 22, 23",

"date__1" : {"date" : "2024-10-16", "time" : "19:10:00"}

}”) {

id

}

}


It runs successfully under GraphiQL in the Monday Developers space. I have another Make automation that is making a similar multiple column mutation and it’s getting the same parsing error.


Anyone run into this?

Hi @gweisenb,


Since your question focuses more on the API query, I am changing the category so your post goes into the apps & developers queue. Just wanted to give a head’s up 😃


Best,

Rachel

I think the issue might be with how the JSON is formatted in the column_values. Even though it works in GraphiQL, Make.com might be handling it differently.


Try to escape the double quotes inside the column_values JSON, like this:


column_values: "{\\"text__1\\": \\"18, 19, 20, 21, 22, 23, 18, 19, 20, 21, 22, 23\\",\\"date__1\\": {\\"date\\": \\"2024-10-16\\", \\"time\\": \\"19:10:00\\"}}"

Also, make sure there aren’t any line breaks or weird characters in there. Sometimes platforms don’t handle line breaks well in strings.

Hey I happened to me as well.


All of a sudden it crushes every time.


@rachelatmonday Can you please check if there has been an update to the API that affects the change_multiple_column_values call?

I see in status.monday.com that there was a scheduled maintenance few days back, can it be related to this error?


Thanks!

image

Make.com tech supports thinks it’s something on their end. You’ll want to report it to them so they start to compile a record of incidents. In the meantime, review the structure of the JSON and try to make it “compact”. Here’s what they sent me:


image


I’ve tried multiple times for them to be very specific about where they made the change. No luck so this screenshot is the best I have. From there, it’s a bit of trial and error.

+1 here


on create_update I get this error response

image


The update body I am sending is pretty much the same as any other till a few days ago:

{"query":"mutation {create_update (item_id: 1681046262, body: \\"\\n <p><b>Ticket description (imported FD message from client):\\n </b> \\\\n <div style=\\\\\\"font-family:-apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Helvetica Neue, Arial, sans-serif; font-size:14px\\\\\\"><div style=\\\\\\"font-family:-apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Helvetica Neue, Arial, sans-serif; font-size:14px\\\\\\"><div dir=\\\\\\"ltr\\\\\\">TEst message</div><div dir=\\\\\\"ltr\\\\\\"><strong dir=\\\\\\"ltr\\\\\\">TEst test message&nbsp;</strong></div></div></div> \\\\n \\\\n <b>Comment from Agent:</b> \\\\nTEst test\\\\n</p>\\") { id }}"}

For everyone facing this issue, it is likely due to an upgraded parser. You can find more details here!

Reply


Terms & ConditionsCookie settings