Hey! Anyone know what to do when your zap transfers come back with this error - For Context, the zap is working currently, but i need to get the prior data - How do you troubleshoot this? This is for a Facebook to Everyaction flow with some javascript in between.
Cannot destructure property 'name' of 'e.find(...)' as it is undefined.
Thanks in advance!
Hi
I looked into this and found that there’s a known bug that we’ve identified. I’ve added you as an affected user, so when it’s resolved you’ll be notified via email.
In the meantime, I found reports of customers who saw this error when using a Zap with Paths. They were able to successfully work around this error by splitting the "Paths" Zap up into separate Zaps (using Filters), with each separate Zap handling the actions that were previously handled in each Path.
Maybe give that a try to see if it helps?
Thanks
Hi
I’ve added you to the list of affected users. Thanks! We’ll send you an email once there’s any update available.
Hi
I’m having the same problem using paths too
Thanks for letting us know
Same here… cannot use path :/
Hi
I’ve added you to the lists of affected users. We’ll update you via email once available. Thanks!
Same for me as well. You can add me to the list too.
Hi
I’ve added you to the list of affected users, we’ll send you an email once an update is available. Thanks!
I’m having this issue as well. Can I get added to the list of affected users as well?
Thanks
Hi
I’ve added you to the list of affected user. We’ll update you via email once available. Thanks!
Ah, sorry to hear that workaround didn’t work for you, 
I went ahead and added you as an impacted user to this report.
Totally understand this isn’t ideal and really appreciate everyones patience. I’m digging into this with the team and hopefully we’ll have an update for ya’ll soon.
Can you add us as an affected user as well please, thanks.
Same here. Any update on this
Hi
I’ve added you guys to the list of affected users. So far, we don’t have any update regarding the issue but rest assured that we will keep this thread up to date and send an email to all affected users once available. Thanks!
Please add me to the affected user list. Thank you kindly
Hi
I’ve added you to the list of affected users, and we’ll send you an email once an update is available. Thanks!
Please can you update us on when this will be fixed? It is making things quite difficult at the moment given that it worked, was relied upon and then suddenly stopped working.
Having the same issue, and my zap with paths is too complicated to divide, so please add me on the list, too. Thanks!
Having the same issue, and my zap with paths is too complicated to divide, so please add me on the list, too. Thanks!
One more thing: Do you have a rough time schedule for the fix? Are we talking about days, weeks, or months? My colleague who now has to transfer all the data manually is asking… :-)
Hi, I’m suffering from the same issue and my zap uses paths. Please add me to the list. thanks!
Hi
I’ve added all of you to the list of affected users. We will keep this thread up to date and send an email to all affected users once available. Thanks!
Hi
I looked into this and found that there’s a known bug that we’ve identified. I’ve added you as an affected user, so when it’s resolved you’ll be notified via email.
In the meantime, I found reports of customers who saw this error when using a Zap with Paths. They were able to successfully work around this error by splitting the "Paths" Zap up into separate Zaps (using Filters), with each separate Zap handling the actions that were previously handled in each Path.
Maybe give that a try to see if it helps?
Hey community friends! I wanted to let ya’ll know this has been escalated and our team is working on a fix. Hopefully we’ll have some good news for ya’ll in the next few weeks.
We truly appreciate everyones patience and we’ll continue to keep everyone in the loop as we know more!
Hi
I looked into this and found that there’s a known bug that we’ve identified. I’ve added you as an affected user, so when it’s resolved you’ll be notified via email.
In the meantime, I found reports of customers who saw this error when using a Zap with Paths. They were able to successfully work around this error by splitting the "Paths" Zap up into separate Zaps (using Filters), with each separate Zap handling the actions that were previously handled in each Path.
Maybe give that a try to see if it helps?
Hey community friends! I wanted to let ya’ll know this has been escalated and our team is working on a fix. Hopefully we’ll have some good news for ya’ll in the next few weeks.
We truly appreciate everyones patience and we’ll continue to keep everyone in the loop as we know more!
Welp. Back sooner than expected!
The team confirmed this should be resolved and impacted users notified via email! You’ll now see Paths as your destination integration in the main Transfer window!
As a heads up, depending on the path your zap takes, we’re not able to determine how many tasks you may use. So feel free to disregard the Duration & Cost columns for now - more design updates for this are on the way.
If you’re still running into this error, please send our support team an email and they’ll be happy to look into it. 
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.