Persistent Timeouts with Pabbly API

[ugavetdude]

Your Workflow URL

IjU3NjYwNTY1MDYzMjA0M2M1MjZiNTUzYzUxMzUi_pc

Your Task History ID

IjU3NjUwNTZiMDYzZTA0MzY1MjZhNTUzNTUxMzY1MTY2NTQzNTBmMzQi_pc

Consent to Access & Modify

I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.

Hello Pabbly Team,

I was having persistent timeout problems with Gemini, but this has been largely solved by your team. I'm very thankful for you guys solving it. I know the timeout period was increased to 100s. That thread is here: https://forum.pabbly.com/threads/pe...-google-gemini-integration.32539/#post-152116

I'm now running into a timeout issue with Deepgram (referencing using the Pabbly API) using the same workflow.

I would use the native Deepgram integration but you don't support the latest model (Nova-3) in addition to 'keyterm' functions to reduce transcription errors with common words. So I use the API instead.

The API is timing out at 25s. I didn't have this issue previously, but it's happening several times a day now. And my transcription requests aren't any longer than they have been in the past.

I'm also using a delay (with a random number generated to create variation in the delay) before the Deepgram API call.

Can you please increase this to at least 40 seconds, or better yet, 50 seconds?

Thank you!

 

[Preeti Paryani]

Hello @ugavetdude,

Unfortunately, we are unable to increase the timeout for the API (Pabbly) application. We recommend reaching out to the Deepgram team to optimize the response time for your requests.

Please note that if a task fails, the auto re-execution feature may capture the response in a subsequent attempt. There was an issue with auto re-execution previously, but our team has recently fixed it. Kindly check your later task history to see if auto re-execution helps in your case.

Thank you for your understanding.