Dust Community Icon

Home
Events
Groups
Members

Announcements
Feedback
Help

Documentation

Powered by Tightknit

How to Increase Zapier Timeout for Document Processing Tasks | Dust Community

How to Increase Zapier Timeout for Document Processing Tasks

·Feb 03, 2025 02:43 PM·

Hey team, I often run into this error on Zapier because my assistant processes a large number of documents and takes some time to generate a response. Is there a way to make Zapier wait longer for the assistant to complete its generation? Thanks!

7 comments

· Sorted by Oldest

Remi
·
·
Hey Josselin Davy 👋 I don't think so unfortunately. Maybe you could try plugging faster models to your assistant? cc Alban
Alban
·
·
Hi, yes unfortunatly zapier has a 30 seconds hard limit. We also have a pipedream integration that lets you pick your timeouts (you pay per second, so they don't care if your workflows run longer)
Josselin Davy
·
·
Got it! Apparently, a workaround is to use a webhook-based callback to handle the action asynchronously. https://docs.zapier.com/platform/build/troubleshoot-action-timeouts
Damien Boyer
·
·
I've the same problem here, do you tried to use your solution Josselin Davy with webhook callback ?
Josselin Davy
·
·
Damien Boyer I’m currently testing an HTTP request in Make because it allows increasing the timeout up to 300 seconds. I’ll let you know if it works. Otherwise, in Make, you can use the Dust Integration, which has a 40-second timeout (10 seconds more than Zapier), if that helps.
Damien Boyer
·
·
Thanks I'm going to try Make 👌
Alban
·
·
Again pipedream is really good for that 👍
🤩1