Pega Pulse Notification Issue - no new notifications
Hello Pega community, OOTB Pega Notification worked fine for Dev and Preprod envs but in the production we are not able to see any new notification in the notification rubrique , since 18th of december 2024, when I post any thing pulse/Task and no email notification is sent/recieved.
No instance in pega-notification is created as well. I checked already: -The smtp server is OK. -The email is enabled in the notification configuration (as shown in the screenshoot attached). -The good email account is configured and used. -Pega ProCom background processing agent is validated and resaved as recommended in one ticket in pega support For info, we are using OOTB rules and no recent changes are done on related rules. Any suggestion why its not working, please?
HCA Healthcare
US
Since you've already checked the SMTP server, email configurations, and the ProCom agent, here are a few more steps you can try: First, review the Pega logs in the production environment for any errors related to notifications; this can reveal hidden issues. Next, ensure that all scheduled jobs and background processes related to notifications are running correctly in production. It’s also a good idea to compare the configuration settings between your working environments and production to spot any discrepancies. Check that the user roles and permissions in production allow for sending and receiving notifications. Additionally, verify that there haven’t been any recent system updates or patches in production that might have affected the notification functionality. Make sure the production database has all the necessary tables and entries for notifications to be created. It might help to clear any caches or restart the application server to see if that resolves the issue. Also, confirm there are no network or firewall settings in production blocking the notification services. If everything seems correct but the problem persists, consider reaching out to Pega support again with detailed log information. By systematically checking these areas, you should be able to identify and fix the notification issue in your production env.