Email hook
Status: Closed · Asked by Scott Bousfield on · 0 views
Hello Scott,
Thank you for sharing the details, and please be assured that we will not make any changes to your workflow without contacting you first.
Upon checking the workflow and its Task History, we can see that it is currently working fine and the emails are being received and processed successfully. At the moment, we do not see any specific issue with the Email Parser trigger or the workflow.
IPabbly Support:
Hello Scott,Thank you for sharing the details, and please be assured that we will not make any changes to your workflow without contacting you first.Upon checking the workflow and its Task History, we can see that it is currently working fine and the emails are being received and processed successfu
It's currently working because I cloned the original workflow, changed the Trigger to something else, saved the workflow and then changed the Trigger back to Email Parser. This created a new pcmailhook.com email address. I was then able to log into my Gmail and setup the new forwarding address from the Pabbly Email Parser.
My problem was I needed to pause or disable the workflow while I made changes to the Omada Site logging. I disabled the workflow, made the changes to my Omada Site logging and then enabled the workflow. This did not work. When I enabled the workflow, the Email Parser (Pabbly) stopped responding to incoming emails. What I don't know is if the issue was with the Pabbly workflow or with pcmailhook.com.
I would like to be able to temporarily disable the workflow, make changes to my Omada system, re-enable the workflow and have it continue working. Should this not be possible?
Bear in mind the changes I'm doing in the Omada system is only what it's logging - it continues to send all log events to my Gmail account even as I'm making changes. I only want to temporarily disable the Pabbly Workflow so I don't get inundated with text messages while I test the Omada logging changes.
Hello Scott,
Thank you for the detailed explanation.
We understand the issue now. You temporarily disabled the workflow while making changes to the Omada logging configuration, and after re-enabling the workflow, the Pabbly Email Parser stopped responding to incoming emails. You were able to restore it by cloning the workflow and generating a new Email Parser address.
We’ll check this behavior further to determine why the Email Parser stopped responding after the workflow was re-enabled and whether the issue was related to the workflow or the Email Parser service.
We’ll review this with the concerned team and get back to you with an update.
Hello Scott,
Thank you for your patience while our team investigated this issue.
The team has identified the issue with the Pabbly Email Parser, and the fix has now been deployed to production.
You should now be able to disable and re-enable your workflow without losing Email Parser functionality. The existing pcmailhook.com Email Parser address should continue working after the workflow is re-enabled, so there should be no need to clone the workflow or generate a new parser address.
Please test this with your existing workflow by:
Disabling the workflow.
Making the required changes to your Omada logging.
Re-enabling the workflow.
Sending a test email to the Gmail address configured for Email Parser.
Checking whether the workflow receives and processes the email.
Please let us know the result after testing. If you still face any issues, share the latest Task History ID, and we'll check it further.