Our job that fetches the conversations rely on the conversationEnd to be included in the Interval, before it was working like this, pretty much how this topic is explaining Interval difference, but now if the conversationStart is not in the interval range we don't return it anymore, since when it's changed?
Can we get back the old behaviour adding something like a boolean param considerAllEventsInTheInterval
This is how it's described in the documentation currently:
Specifies the date and time range of data being queried. Results will only include conversations that started on a day touched by the interval. Intervals are represented as an ISO-8601 string. For example: YYYY-MM-DDThh:mm:ss/YYYY-MM-DDThh:mm:ss
If the API is behaving in a way inconsistent with the documentation or has changed without any official announcement of that intended change that should be reported through a customer care incident.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.