To whom it may concern,
I’m using PhantomBuster in one of my Zaps. It appears to respond later than 30 seconds sometimes.
In such cases the Zap is going to raise an error. I looked into PhantomBuster logs and realized in these cases the response time is just a little bit higher than Zappier limits.
I understand that Zappier can't wait too long for third party apps, but in my observations, increasing the waiting time for PhantomBuster from 30seconds to just 45seconds is enough for doing the job.
I looked into Zappier's community and realized that I'm not the only one having this problem. Of course 45 seconds might not be sufficient for some users but will definitely solve the issue, some of them are having.
I appreciate your comprehension
Looking forward for good news form you
Best answer by DanversView original
Can you post the screenshot of your Zap? Also, Can you even post the screenshot of the error?
Like you say, this has been requested more often by the community but most likely won’t change any time soon. However, what you could try to do as a workaround / fix is using webhooks on phantombuster:
You can read about this here: https://hub.phantombuster.com/docs/using-webhooks
Hope this helps.
Thanks for reaching out about this and welcome to the Community! :)
I’ve been looking into this and it seems there’s an existing bug report open for this behaviour with the PhantomBuster app integration. So I’ve added you to the list of affected users. I don’t have an ETA but we’ll send you an email notification as soon as the app’s developers are able to resolve the issue.
In the meantime, if a PhantomBuster step does hit that timeout error, if you try replaying that errored run of the Zap a little while later, it may then be able to go through successfully. Hope that helps!
If anyone is trying to do the same thing, @JCM found a workaround for this using webhooks. They explain it in their post here: Work Around PhantomBuster didn't respond in time error