Open vendoshi opened 3 weeks ago
We are facing exactly the same issue. and if you notice in this specific event there is no event name, which collect a lot of unnamed events in the failure to mixpanel.
There is a temporary workaround. We can manually change the mapping in segment.
Here I have mapped receivedAt
with timestamp instead of existing timestamp. This is working for me.
Context
When attempting to send an event from Segment Analytics in our Flutter app, the event timestamp appears to be set in the future, causing the event to fail in Mixpanel with a 400 Bad Request error. This issue is likely due to a timestamp misalignment within the Flutter package.
Reproduction Steps:
Testing with Event Tester in Segment
Event Example Input
Error Response from Mixpanel:
Details: In the input, the sentAt field (2024-10-31T17:50:15.238Z) is accurate, but the timestamp field (2024-10-31T23:20:10.615Z) is incorrectly set in the future. Mixpanel requires the event timestamp to be valid and within the current time frame, resulting in this failure.
Suspected Cause: This appears to be due to a potential timezone-related issue in the Segment Analytics Flutter SDK, where the timestamp is not being correctly synchronized with sentAt based on the device timezone.
Expected Outcome: The timestamp should be aligned with the actual event time (sentAt) to prevent Mixpanel from rejecting events due to a future-dated timestamp.