Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X
Hello community,
Email notifications are not being triggered for Alarm events. I have successfully configured the alarms, and the events are being triggered as expected, visible in the UI. However, I am not receiving the corresponding email notifications.
I have verified that the mail server was properly configured, and I tested it by sending a test email by executing send message service in PTC.FSU.CORE.Notification.Notification_TG Thing.
Has anyone else encountered a similar issue? Any input or assistance would be greatly appreciated.
Thanks!
Solved! Go to Solution.
Thank you Seb for your response!
I have received information from the support team that the subscriptions responsible for triggering email notifications were disabled in PTC.FSU.CORE.Process.ProcessQueue_TM. After enabling these subscriptions, the email notifications are now functioning properly.
Appreciate your help here!
To keep the community informed about this issue, I am marking it as the solution.
Hey @AR_10412166
it might be an issue with the spam blocker on our email account.
I had issues in the past where automatic email's from ThingWorx would not come through because of a spam blocker.
Even if you received the email that sent manually using the SendMail service on the Thing, many spam blocker are also looking at the syntax of the message and not only on the sender.
You could try the following, add the email account that you have configured as sender in AMU, as contact in our email account.
You can also try to change the message content in the AMU alert configuration, to be different from the default.
Seb
Thank you Seb for your response!
I have received information from the support team that the subscriptions responsible for triggering email notifications were disabled in PTC.FSU.CORE.Process.ProcessQueue_TM. After enabling these subscriptions, the email notifications are now functioning properly.
Appreciate your help here!
To keep the community informed about this issue, I am marking it as the solution.