Keep getting API response timeouts due to 25 second rule

[slade84]

Your Task History ID

IjU3NjYwNTZlMDYzMzA0MzI1MjZjNTUzZDUxMzUi_pc

Hi guys,

How do I implement the workaround so that my API request can take longer than 25 seconds? I'm not understanding where/when to implement the delay mentioned in this thread: https://forum.pabbly.com/threads/pa...rror-response-not-received-in-25-seconds.855/

 

[ArshilAhmad]

Hi @slade84,

In step 3 of your workflow, you appear to be making a POST request. The application whose endpoint you are executing may take more than 25 seconds to process the request and send a response back to Pabbly Connect, which results in the "Response Not Received in 25 Seconds" error.

The documentation states that the application should immediately send a response to Pabbly Connect without processing the POST request. This prevents the "Response Not Received in 25 Seconds" error. You can then add a Delay as step 4 of your workflow to allow the application enough time to process the POST request. After the delay, execute another endpoint with a GET request to fetch the processed information.

 

[Fagun Shah]

Hi guys,

How do I implement the workaround so that my API request can take longer than 25 seconds? I'm not understanding where/when to implement the delay mentioned in this thread: https://forum.pabbly.com/threads/pa...rror-response-not-received-in-25-seconds.855/

What app's api you're trying?

 

[slade84]

Hi @slade84,

In step 3 of your workflow, you appear to be making a POST request. The application whose endpoint you are executing may take more than 25 seconds to process the request and send a response back to Pabbly Connect, which results in the "Response Not Received in 25 Seconds" error.

The documentation states that the application should immediately send a response to Pabbly Connect without processing the POST request. This prevents the "Response Not Received in 25 Seconds" error. You can then add a Delay as step 4 of your workflow to allow the application enough time to process the POST request. After the delay, execute another endpoint with a GET request to fetch the processed information.

@ArshilAhmad how do I get it to immediately send a response back? Here is their documentation: https://afforai.com/documentation#post-/completion

What app's api you're trying?

@Fagun Shah it's afforai.com. It's an AI research tool, so it will always take a long time because it has to sift through a few hundred documents to find the answer and send it back. So, I need to give it time to respond.

 

[Fagun Shah]

@ArshilAhmad how do I get it to immediately send a response back? Here is their documentation: https://afforai.com/documentation#post-/completion




@Fagun Shah it's afforai.com. It's an AI research tool, so it will always take a long time because it has to sift through a few hundred documents to find the answer and send it back. So, I need to give it time to respond.

Ohk, in afforai case there are only 2 options for you,

1. Ask pabbly team to increase your custom app's timeout limit
2. Ask Afforai team to add webhook support or provide Get Request by Id endpoint which you can call later in the same workflow after Delay action

I am actually always recommending pabbly team to introduce timeout based task usage, like if it takes 25-seconds or less use 1 task, if it uses between 25-50 then use 2 tasks and so on. But currently this is not available which limits use of AI models in pabbly connect.