Skip to main content

I’m using the Graphql API to update Monday - but it behaves inconsistently and doesn’t always perform the update.

I’ve noticed in my log, that in some calls to the change_column_value mutation, it returns undefined - I think these are the cases where it doesn’t save the change, but it’s all very inconsistent - because if I call it again, it does save.


What are the cases where change_column_value returns undefined?

Should I add logic that will repeat the update until it doesn’t return undefined?


Here’s the graphql:


      mutation ($id: Int!,$value:JSON!,$board:Int!,$column_id:String!) {
change_column_value(
item_id:$id
column_id:$column_id,
board_id:$board,
value:$value
) {
id
name,
column_values(ids:m$column_id]){
id
value
}
}
}

Here’s a link to my code on github:

github.com

I would love to hear from you

Hello @noam.honig and welcome to the community!


I hope you like it here 💪


I’m curious about the response you are getting. Can you please send the full response you get from our server with the full message and error code? A screenshot would also do.


Looking forward to hearing from you 🙂


Cheers,

Matias


I added some console logs to my server - I’ll send you the info next time this problem occurs


Hello again,


Sounds good!


I see now that the result in these cases returns an errors object with more info - I’ll follow its info and work accordingly.


I must have missed that in the docs (if you can share a link to these docs, I’ll appreciate it.


Thanks


Hello @noam.honig,


I am glad you found the information about the error in the response.


Here is the documentation you can check about it.


Let us know if you have other questions!


Cheers,

Matias


Reply