Hi @Jorge_Artave Welcome to the forum
The bug essentially is that when listing conversations and sorting them by
created_at, there can be some conversations which are returned with a timestamp value that is out of order with respect to the rest
Is this bug restricted to Conversations? Are Users affected by this?
The issue that we have documented internally only affects Conversations. If you are seeing it on users, do share some details on it here (or if it contains possible user information do share it with us in our Messenger / chat)
Do you think ‘page size’ parameter has any relation with the issue?
Page size is not a factor in relation to the issue
This seems to be happening with created_at, is there any other property that might be affected as well?
created_at are affected. Currently I’m double checking to see if
waiting_since is affected and will give you an update when I have it
Does it affect the scroll api?
The scroll API is only for users, leads and companies and not conversations so it isn’t affected by the same issue
Is there anything that we can do to mitigate this behavior?
Not at the moment. The issue lies in the backend
Is this planned to be fixed in the listing API? ETA?
Yes it is being planed, but no specific ETA at the moment. If you send us a message via Intercom we can add you to the tracking issue so that we can reach out when it is fixed
Is there any other API that we could use to gather this data (Bulk or similar)?
Depending on the data you’re looking to extract there could be ways to what you need so please share a bit of details and I’ll see what can be done
Our initial guess was that this happened to some sporadic conversations but found out multiple consecutive missplaced conversations. Do you think there might be a pattern (for instance. misplaced conversations will be coming in batches of 5 or fewer conversations)?
The issue lies in our data in the backend and how we update the data based on different interactions. I think this situation could be coincidental and perhaps those conversations had similar interactions which caused the same kind of updates to happen