Question
how does email listener handle the error queue
Hi Team,
Can anyone please provide clarification regarding handling of error queue in email listener.
My Requirement:
When an email comes to a particular configured email id, it should create a case.
But whenever an email is coming,the case is getting created and error count is also getting increased. As a result, multiple cases are getting created for a single email.
Regards,
Divya Sri Padarthy.
Message was edited by: Marissa Rogers - Added Category, moved from Mesh Help
Accepted Solution
If your EmailListener is configured to reply and that reply fails for some reason, the email will not be marked seen and thus will get processed again. Turn debug on EmailListener class and read through the log file to see if that is happening.
Thanks Gangababu and Vipin.
But the issue we are facing is even in successful processing, the error count is getting increased. So that it is creating multiple duplicates.
So i just wanted to know when the process is considered as an error and how many times will it retry.
There is no specific limit for retrying in email listener unlike in file listener. As long as mail is in unread format, email listener will try to process the email and perform the action specified.
Please turn on the debug level loggers on Email Listener class. It will give you some clue.
email loggers...
- com.pega.pegarules.services.emaillistener
- com.pega.pegarules.integration.engine.internal.services.email.EmailListener
Thank You Gangababu and Phani.
your replies helped me to resolve my issue .
As far as I know there is no queue mechanism in Email Listener data instance.
Ideally Email Listener listens on a particular folder(Let's say Inbox), whenever incoming email reaches the inbox, email listener starts processing the email and perform the operations mentioned in Email Service Activity. Once email gets processed it should go to read process and Email Listener won't be able to access again.
pyCreateAndManageWorkFromEmail OOB activity creates a case upon receiving the new email. Use this activity and test your scenario.
https://pdn.pega.com/sites/pdn.pega.com/files/help_v72/procomhelpmain.htm#data-/data-admin-/data-admin-connect-/data-admin-connect-emaillistener/propertiestab.htm