Hi Library friends!
A customer of ours is using ruby to send events to amplitude with the order of identify->group->track. Due to the rate of the events firing, the generic 'timestamp' and 'receivedat' timestamp field are often the same down to the millisecond, as you can see in the Segment S3 logs:
After speaking with the libraries engineering team it was advised to submit a request for our Ruby engineers to update the timestamps to become even more granular to avoid this error.
Hi Library friends!
A customer of ours is using ruby to send events to amplitude with the order of identify->group->track. Due to the rate of the events firing, the generic 'timestamp' and 'receivedat' timestamp field are often the same down to the millisecond, as you can see in the Segment S3 logs:
After speaking with the libraries engineering team it was advised to submit a request for our Ruby engineers to update the timestamps to become even more granular to avoid this error.