Getting this"Response not received in 25 seconds" error message

[Aditya Gaikwad]

Hi team,


We’re facing an issue with one of our automations where ManyChat sends data to a Pabbly webhook (which is the trigger module). Occasionally, this webhook does not show up in the workflow history, and the automation doesn’t run at all.


We also received this error message:
“Response not received in 25 seconds”
(I’ve attached the screenshot for your reference.)


Can you please confirm:

1. Does this error mean Pabbly received the webhook but failed to process it in time?
2. Or is it possible that the webhook didn’t reach Pabbly at all from ManyChat?

We just want to ensure that the webhook trigger is reliable. If it’s a timeout issue on Pabbly’s side, is there a recommended way to prevent this — like splitting the flow or using a buffer?


Thanks

 

[Soumya Tripathi]

Hello @Aditya Gaikwad
Kindly let us know your workflow ID, so that we can assist you accordingly.

Please be aware that to assist you effectively, we may need to access your Pabbly Connect account. If you're comfortable with this, please grant us permission by stating in your next email: "You have my permission to log into my Pabbly Connect account, and edit workflow {If required}. Here is the registered email address associated with it."

 

[Aditya Gaikwad]

You have my permission to log into my Pabbly Connect account, and edit workflow {If required}. Here is the registered email address associated with it.- [email protected]

workflow Id - IjU3NjYwNTY4MDYzNDA0MzY1MjZjNTUzNTUxMzQi_pc

 

[ArshilAhmad]

Please share the Task History ID where you received the “Response not received in 25 seconds” error.

Kindly note that Webhook by Pabbly is based on descriptive webhooks, which means we don’t have any control over the data. We simply provide the webhook URL, and if the source application to which you’ve connected the webhook sends data, it triggers the workflow. If not, the workflow won’t get triggered at all.

 

[Aditya Gaikwad]

Hi team,


Thanks for your response. As requested, here are the details:


Task History ID: IjU3NjUwNTY4MDYzMzA0MzE1MjZhNTUzNTUxMzM1MTY1NTQzNDBmMzki_pc


Workflow Name: SK Sales: New Sale, Recurring, Refund, Cancel


Date/Time of Error: 2025-07-22T12:01:39+00:00


Affected Step: Google Sheets: Add New Row - Shared Ravel Validator


Error Message:
"Response not received in 25 seconds"


This error was captured by Pabbly Connect Manager, but when we checked the workflow's Task History from the main dashboard, we could not find this specific error logged there.


Could you please help clarify:

1. Why this error was not recorded in the Task History, even though it's visible in Connect Manager?
2. Does this indicate that the webhook was triggered correctly, but the Google Sheets step timed out?
3. Is there anything we can do to prevent this issue, such as optimizing the Google Sheet or restructuring the step?

We have attached a screenshot from Pabbly Connect Manager showing the full details of the error. Please let us know if you need anything else to assist further.


Thank you

 

[ArshilAhmad]

The error appears to have been resolved upon re-execution, which is why it is no longer visible.

The issue occurs when an application takes more than 25 seconds to process a request and send a response back to Pabbly Connect. We suggest adding a Delay before the 'Add New Row' action step to see if that resolves the issue.

 

[Aditya Gaikwad]

Thanks team.
I see in Screenshots, you are pointing towards "1".
What does that mean?

and is any chance of getting same error even after using delay before "add row"?

 

[ArshilAhmad]

It means the number of times the workflow was executed before you stopped encountering the error.

You can still get the same error even with the Delay step, but it should help mitigate the issue. As mentioned earlier, the issue occurs when Google Sheets fails to process a request and takes longer than 25 seconds to send a response back to Pabbly Connect. Since the source application is unable to respond within the required timeframe, we can only suggest workarounds to minimize the chances of this error.