Never happened to me.... the order of the activities in a case (and variant) is first by eventtime, then by sorting if both eventimes are equal.... only explanation is that new data has been ingested for those cases with eventime (or eventime more detailed, like including the seconds) , so no longer they have the same timestamp and they ignore the sorting
HTH
Hi Guillermo,
thanks for your reply. I double checked the timestamps in my underlying data. And there are actually a few timestamps that even include milliseconds instead of only seconds. This must be the cause of the problem.
The tricky problem was: I am doing manual Excel File Upload. And the timestamps in my Excel file sometimes include milliseconds, sometimes not. However, if i upload the data in Celonis and run a SELECT Query, the timestamps are always displayed in the same format without milliseconds. SInce i only took a look at the SELECT Query, i didn't notice in the first place.
Now i either need to clean my underlying Excel data or adjust the timestamp schema in the file upload section.
Thanks for your quick reply
Fynn
Hi Guillermo,
thanks for your reply. I double checked the timestamps in my underlying data. And there are actually a few timestamps that even include milliseconds instead of only seconds. This must be the cause of the problem.
The tricky problem was: I am doing manual Excel File Upload. And the timestamps in my Excel file sometimes include milliseconds, sometimes not. However, if i upload the data in Celonis and run a SELECT Query, the timestamps are always displayed in the same format without milliseconds. SInce i only took a look at the SELECT Query, i didn't notice in the first place.
Now i either need to clean my underlying Excel data or adjust the timestamp schema in the file upload section.
Thanks for your quick reply
Fynn
Yep, we found yesterday the problem that the output of a SELECT doesn't show millisecs
We used this as workaround to see the millisecs: select modifyts || '.' || EXTRACT(MILLISECONDS From modifyts)
...modifyts is the timestamp variable in our case.
https://www.vertica.com/docs/9.2.x/HTML/Content/Authoring/SQLReferenceManual/Functions/Date-Time/EXTRACT.htm?Highlight=extract
(there are other functions in Vertica, but it seems they haven't been implemented in Celonis)
Yep, we found yesterday the problem that the output of a SELECT doesn't show millisecs
We used this as workaround to see the millisecs: select modifyts || '.' || EXTRACT(MILLISECONDS From modifyts)
...modifyts is the timestamp variable in our case.
https://www.vertica.com/docs/9.2.x/HTML/Content/Authoring/SQLReferenceManual/Functions/Date-Time/EXTRACT.htm?Highlight=extract
(there are other functions in Vertica, but it seems they haven't been implemented in Celonis)
Ok, thanks for the info. I now solved the problem by simply removing the millisecond timestamps, because they occur so irregularly in my Excel Data. I did this by changing the timestamp schema from 'yyyy-MM-dd HH
ss.SSS' to 'yyyy-MM-dd HHss'
