@umamaheswar.bk  

as you have not had any response, I will provide some input.  

NOTE: The below answer came from a GenAI tool. 

It is imperative you check the References used to come with this answer.

-------------------------------------------------------------------------

The main challenge here is that when using the same email address across multiple environments (Dev and QA), you need to ensure each environment has its own dedicated email listener configuration. Let me explain what's likely happening and how to resolve it:

Why It's Not Working

When you deploy an email bot from Dev to QA while using the same email address, the following issues can occur:

1. Listener Conflict: Each environment needs its own dedicated instance of the email account and email listener. You cannot use the same email listener for multiple environments.
2. Environment-Specific Settings: Even though you're using the same email address, QA-specific configurations might be missing or incorrectly set up.
3. Email Account Association: The email account might still be associated with the Dev environment or another channel in your QA system.

Steps to Fix the Issue

Here's what you need to configure in your QA environment to make the email bot work:

1. Create a Dedicated Email Listener for QA:
   • In Dev Studio, navigate to Records > Integration-Resources > Email Listener
   • Click "Create" to set up a new listener specifically for your QA environment
   • Provide a name and description that clearly identifies it as the QA listener
2. Configure Email Account Settings:
   • Verify that the email account is properly configured in QA
   • Ensure all email server details for sending and receiving are correctly set up
   • In the Email handling section, click "Add email account" and select the email account
3. Set Listener Properties:
   • Specify the email account from which to pull emails
   • Set the frequency for checking the inbox
   • Configure email service rules for routing
4. Verify and Test:
   • Click "Verify" under the email account list to confirm the listener is established
   • Send a test email to check if the bot processes it correctly
   • Check logs for any errors or issues
5. Restart the Service:
   • After making configuration changes, stop and restart the email listener service
   • This ensures all changes take effect properly

It's important to note that Pega recommends configuring only one email listener to monitor an email account. Having multiple listeners monitoring the same inbox can result in throttling and inconsistent results. Since you're using the same email for both environments, you'll need to ensure only one environment's listener is active at a time, or consider using different email addresses for each environment in the future.

[References:

Troubleshooting email accounts in the Email channel

Configuring email listener routing