The format for some of the responses we receive for conversationEnd or conversationStart will be missing the milliseconds within the value for those fields. This breaks the process that we currently have in place to process the data pulled from the API as we're expecting the values to follow a standard format. Is this a known issue? Under what circumstances would the milliseconds be dropped from the corresponding value?
The documentation for conversationEnd, and datetimes in general, states the format as yyyy-MM-ddTHH:mm:ss[.mmm]Z. The braces indicate that the fractional seconds are optional; your app will need to be tolerant of this as both with and without are valid ISO-8601 formats.
Thank you for that clarification! The only other question I have pertaining to this is what determines whether or not the milliseconds will be included as a part of the format of any given response? Does it happen when the timing perfectly lines up to be 000 milliseconds or is there some other kind of logic?
The reason I ask is that while our system can tolerate processing these types of fields in both formats, our downstream systems will require a more standardized format. We can append the milliseconds at the end of the value where they are not present but just want to understand the underlying logic for the field format.