christina.d wrote:
nicksimard wrote:
Hi @FF15!
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. 🙂