Issues with Cloned Events in MixPanel Setup for PMs | Mixpanel Community

Issues with Cloned Events in MixPanel Setup for PMs

I am in the process of setting up MixPanel (I am a PM). I set up some custom events, which seemed to then auto-created a cloned event (same name) that doesn't show up in the custom events list, but does show up in the events list. Those cloned events seem to be buggy (not pulling event data for some reason). So then I deleted the custom events to try to clean things up and start over. But the auto-created cloned events are still there, and I don't have a way to delete them. Any thoughts?

🎫1

8 comments

Thena
APP
·
·
Hey Judy- Julianne from Mixpanel Support here. This sounds like a bug on our end. I've gone ahead and asked engineering to take a look at this behavior. I'll let you know once I have more information!
Judy K.
·
·
Thanks Juliane-- appreciate it. I started the process over with some new custom events and same thing is happening. It is automatically cloning the custom events as a separate event (which doesn't work correctly), and cluttering up the Events list. Keep me posted wrt troubleshooting.
Thena
APP
·
·
Happy to help! Did you apply tags to the custom events? It seems like the bug may be specifically related to that workflow. If not, did you take any actions on the custom events after they were created? Engineering can delete the duplicated events from the event table. Can you submit a ticket via our webform that includes the project and event names that should be removed?
Judy K.
·
·
Yes, I did apply tags to the events.
Judy K.
·
·
Will put a ticket together in a bit. How can I avoid this bug going forward? Do I have to not use tags? Or can Eng fix the underlying bug?
Thena
APP
·
·
Engineering is working on a fix for the issue. If you want to apply tags in the meantime, the bug only affects bulk adding them. This means you can add tags directly on the custom event page without seeing the buggy behavior. Inline Attachment: image.png
Judy K.
·
·
Thanks!
Thena
APP
·
·
Engineering pushed a fix for this issue. Bulk tagging custom events now works as expected and doesn't generate any actual events. Thank you for flagging this to us!