https://linen.dev logo
Join Slack
Powered by
We experiencing issues with Mixpanel destination. ...
# support
b
We experiencing issues with Mixpanel destination. We can see upcoming events from Webhook, but at the end Events are not send to Mixpanel for the last two days. To whom I may contact?
m
Hey There! 👋 Your message has been received by the RudderStack team. We will forward this request to your Technical Account Manager, and they will get back to you shortly. Please use the thread for any additional comments.
g
Just jumping on this as we've also seen the same. A good handful of events are seemingly 48hrs +/- delayed in our case. https://rudderstack.slack.com/archives/C01E4PLB135/p1684402419481489
b
We have the same issue about 48 hours
g
Checking with the team if there're any known issues for Mixpanel destination
@billions-umbrella-15053 are you using the RudderStack cloud or the open-source version?
b
@gentle-petabyte-80785 using cloud version
g
I checked with the team, there has been no incident with the RudderStack system or Mixpanel destination. To debug further, please help me with more info 1. What triggered this issue? Was it working earlier and then stopped suddenly? 2. What do you see in 
Live events
tab for mixpanel destination? Any failures? 3. Do you have any transformation applied to mixpanel destination?
b
Very very strange as it working already over couple months and suddenly 3rd day it does not working.
Lets do another test in transformation where Ill send test
Screenshot 2023-05-20 at 10.28.12.png
As we can see test pass successful. But Event did not appear in Mixpanel
Screenshot 2023-05-20 at 10.37.30.png
No event after 6 min received from RudderStack
As we can see profile properties updated because within script Im updating them by calling directly via API, but Event did not submitted by RS Destination.
Screenshot 2023-05-20 at 10.47.43.png
Here is the screenshot of APP that send RS Webhook and it show SUCCESS status, but I dont see any updates on RS stack and Mixpanel site.
Screenshot 2023-05-20 at 11.02.32.png
I have see Event it look like it pass successfully, but I can not see Event registered on Mixpanel
and on RS dashboard; no any notification what is wrong, etc..
We have several pipelines: 1. Webhook (fingerprint) > RS Transformation > Mixpanel (Events) 2. Webhook (Shopify) > RS Transformation > Mixpanel (Events) All pipelines just stop working 3 rd day. And I can not find any error from Source or RS transformation script.
This info maybe can help you to look at. I can see incoming events if I choose from Source node, but if I select incoming events in Transformations I don’t see any. I guess here can be some root cause of problem we speaking. Maybe my transformations blocked on RS side, etc..
I have made several tests and found that root-cause is with RS-Transformation. Probably my account on RS side for transformations are limited or something. Because I just created new account configured the same pipeline and it passed as expected.
@gentle-petabyte-80785
g
I see, This is weird. If there was any limitation, you should have seen the warning in the UI at the time of adding the transformation.
Can you share the transformations code here, I will review. And share your workspaceId, I will double check for any limitations on your account
b
No I did not seen any warnings or so.. thats the point..
g
Will look into this. Please share the transformations code and workspaceId.
b
I guess now it starts working. My work around: I just commented some lines in transformation started test event and saved. After that I again removed comment in transformation and it seems now its working as expected @gorgeous-dream-88338
g
Thanks for the heads up @billions-umbrella-15053! In our case we aren't using any transformations w/ Mixpanel specifically, but I'll check to see if we're still seeing any delay of any sort. It's at least somewhat reassuring if things are looking better your side
👍 1
g
Glad it worked out for you Mantas. I'll try to reproduce the issue to avoid such quirks in future. Feel free to reach out again if you see this behaviour again.
👍 1
Open in Slack
PreviousNext
Powered by