Email Parser (Pabbly): Not Receiving Emails
Status: Open · Asked by Mahesh Babu on · 0 views
It seems that my Email Parser (Pabbly) hasn’t been receiving any new emails for a while now. Has anyone else faced this issue recently or found a fix? We lost at least a 100+ emails because of this.
WE NEED TO FIX THIS.
It seems Pabbly was down for a while. Are you still missing the emails?
Yes, we are. We tried sending emails to the mailbook, but it hasn't recognized anything since last night EST.
This has been down for more than 12 hrs now. And we are struggling to handle emails.
Hello @mahesh_ideations
As we checked, you disabled the workflow on Oct 05, 2025 and then enabled it again. This breaks the connection, so you will need to reconfigure the trigger application: “Email Parser (Pabbly): New Email Received”. Doing this should resolve the issue.
No, we have paused and restarted many workflows during our tenure with Pabbly, never had this issue. We got an official email stating a server outage. You are saying something different. Whom should we trust?
Hello @mahesh_ideations
Could you please let us know where and from whom you received the “server outage” email? We did experience short server downtimes on 06 October 2025 (between 10 AM – 4 PM IST) — around 5–6 times, each lasting 1–2 minutes.
However, as we checked, the workflow was repeatedly disabled and re-enabled since October 05, 2025, which can break the connection and cause the workflow to stop functioning.
To resolve the issue, please reconfigure the trigger application:“Email Parser (Pabbly): New Email Received."
It was not a server outage email; it was a response to our email about this issue from [email protected]. My system is in EST
We may have disabled and re-enabled the workflow when we stopped receiving emails.
Then we put the workflow in capture mode and sent emails to the mailbook email, but didn't receive anything for hours. Then we stopped trying and reported the issue.
And on the 6th, by 4:30 PM EST, the issue resolved itself.
Thank you for the update. We are glad the issue is resolved now.