@ARUNK16936931

Running 650+ email listeners in a Pega application is way too many and likely causing unnecessary load, slower performance, and management headaches. Pega is designed to work best with a small number of listeners usually under 20 by using smart routing and filtering after the email is received. Instead of creating a new listener for every use case, it’s better to use fewer listeners that pull from shared inboxes and then direct the emails to the right process based on subject, content, or sender. You can also handle email parsing outside Pega using cloud functions or queues, and only pass the useful data into Pega. Scaling by adding more listeners is not a sustainable solution it’s a sign that the design needs to be rethought. Keeping things simple and centralized will improve reliability and reduce infrastructure strain.