Attempting to get an item’s updates via GraphQL has broken with the rollout of version 2024-10.
This query would work on version 2024-07, but now does not work. Please try it on the API Playground:
query {
items(ids: [itemIdHere]) {
name
updates(limit: 40) {
creator {
name
}
}
}
}
This same query works fine even with about 190 columns on a board:
query {
items(ids: [itemIdHere]) {
name
column_values {
id
value
text
type
}
}
}
For the first query, lowering the update limit to something like 20 or 25 causes the query to execute properly. Previously in version 2024-07, you could request something very large like 300 updates in one request and it would run just fine.
Why has this functionality been changed? What is the proper process for getting all updates from an item now?
Hello there @aholtzhauer,
That is odd. I ran the query on my end and it works fine.
Would you be able to please fill this form adding as much information as possible to it (such as account ID, board IDs, item IDs, timestamps, etc.) so that our team can take a look into it?
Cheers,
Matias
The issue actually appears to have been resolved as of this past weekend (was still broken Friday but is working now!). The only change it seems that was made in Monday’s API is that when getting Updates, if there was an update created by a Monday automation, the creator is now null, with no fields attributed to it (name, photo_thumb_small, etc)
I’ll go ahead and code around that for now, but I’m not sure if it’s intended or not.
Hey @aholtzhauer,
I checked with the team - the higher limit was causing a timeout internally. They deployed a fix for this on Sunday, so you should be good to go!
Best,
Rachel
1 Like
For anyone else reading this thread - know that if you’re getting updates via the API, the creator
parameter will indeed be null
for an update posted by a Monday Automation, but the creator_id
parameter should return -4 for an Automation.
Other than that, everything should be good to go now!
Thank you for sharing @aholtzhauer !
Sorry to revive an old topic, but… does anyone know why in version “2024-10”, getting updates from an item returns the updates in order from earliest created to last created, as opposed to the default style in “2024-07” and earlier where the first update returned would be the last/most recent update? Is there a way to flip the order retrieved when making the GraphQL request?
The documentation on this page here: (Updates) states “Updates are returned in descending order (newest ones first)”. This holds true when grabbing updates universally from a board, but when grabbing updates from an item, the updates are retrieved in reverse order now. Was this an intentional change?
Hello there @aholtzhauer,
I heard back from the team and the order should be the right one now.
Would you be able to please test it on your end?
Cheers,
Matias