Skip to content

Commit 2bed9eb

Browse files
authored
Merge pull request #5149 from segmentio/courtneyga-patch-3
*updated* RETRY Mixpanel legacy common error
2 parents dfcaaaa + 01cc4c6 commit 2bed9eb

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 a `Timestamp must be within the last 5 years` error, and my timestamp displays `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, Segment converts this to the `1970-01-01` timestamp. If you're experiencing failed events due to this error and you have a connected PHP source, update your PHP Library version to 2.1.0.

0 commit comments

Comments
 (0)