Skip to content

Commit a9d114e

Browse files
authored
RETRY Mixpanel legacy common error
Added a resolution to mitigate the error.
1 parent f4b58c1 commit a9d114e

File tree

1 file changed

+4
-0
lines changed
  • src/connections/destinations/catalog/mixpanel

1 file changed

+4
-0
lines changed

src/connections/destinations/catalog/mixpanel/index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -682,3 +682,7 @@ If you delete an audience or trait in Segment, it isn't deleted from Mixpanel. T
682682
**If a user has multiple external ids in Segment, what happens when they enter an audience or have a computed trait?**
683683

684684
Segment sends an `identify` or a `track` call for each external on the user's account. For example, if a user has three email addresses, and you are sending `identify` calls for your audience, Engage sends three `identify` calls to Mixpanel and adds the latest email address to the user profile as the email “address of record” on the Mixpanel user profile.
685+
686+
**What happens if I receive the following error, "Timestamp must be within the last 5 years." and my timestamp is showing 1970-01-01?**
687+
688+
The Segment PHP Library (2.1.0) version requires a UNIX timestamp. If you send anything other than a UNIX timestamp, it simply converts this to 0 which is the 01-01-1970 timestamp. If you are experiencing failed events due to this error and you have a connected PHP source, please update your version to 2.1.0.

0 commit comments

Comments
 (0)