workflow failed

Status: Closed · Asked by Ryan Muniak on · 0 views

Ryan Muniak — Question ·
Hey team,

One of my workflows failed today and the error looks like it's on your
side, not mine. Wanted to flag it.

Details:

- Step: Google Sheets > Lookup Spreadsheet Rows V3
- Connection: proudfoot fb
- Status code: 500

The error returned was a MongoDB connection failure:

localhost:27017: [Errno 111] Connection refused (configured timeouts:
socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms), Timeout: 5.0s

That's your backend unable to reach its own database, so I don't think
there's anything I can change on my end. My sheet, connection and
credentials were all unchanged and the same workflow had been running
fine.

A few questions:
1. Was there an outage around this time?
2. Is there anything I should change to make the step more resilient to this?
3. Do failed tasks like this retry automatically, or do I need to re-run
   them manually?

This one runs daily for a client, so a failed day means a missed post.
Any guidance would help.

Thanks,

Ryan 
Pabbly Support — Reply ·

Hello,

We have forwarded this concern to our technical team. We will get back to you once we receive an update from them.

Thanks & Regards,
Arshil Ahmad
🌐 Pabbly.com
Pabbly Support — Reply ·

Hello Ryan,

Thank you for your patience.

We identified that the Google Sheets Lookup issue was caused by a temporary downtime of the Pabbly Functions server, which affected some Action Builder-based actions and resulted in the 500/MongoDB connection error.

The issue occurred between 21 August at around 16:33 UTC and 22 August at around 04:51 UTC and has now been resolved. No changes are required from your end.

Please re-run the failed workflow/step to process the missed execution. The Google Sheets Lookup action should work normally now.

If you still face the issue after re-running it, please let us know and we will investigate it further.

Thanks & Regards,
Naman Bansod
Customer Support Specialist
🌐 Pabbly.com
👉 Rate your support

Back to all forum threads · Log in to reply