Skip to main content
17-Peridot
February 8, 2019
Question

Email notification doesn't work

  • February 8, 2019
  • 2 replies
  • 6887 views

Hi experts,

 

I have email extension installed. I create a thing "MyMailServer2" based on it and it works if test it with script. 

However, it doesn't work when I create a entity Notification "EmailNotify" and set  "MyMailServer2" as the handler.  I have no clue about it , could you help ?  

 

===================Updated on Feb 9==============

I didn't figure out the problem above , then I tried to turn to script to send email. So I need to get the recipients defined in the Notification.  I can get the notification content "testNotify" by running the service "GetNotificationContents",  While executing the service "GetUserRecipientsOfEvent" , it tells me no notification conent found(see the Capture5.PNG) .  Any idea about it ? 

 

The Thingworx I installed from : twxFoundationH2Trial-8.3.2-windows-installer.zip

Version of email extension: 3.6.0

 

Regards,

Sean

Thank you 

 

2 replies

22-Sapphire I
February 8, 2019

Are there any errors in the Application Log when the even fires the notification?

seanccc17-PeridotAuthor
17-Peridot
February 9, 2019

No, I checked it but didn't find any error/warning log about it . 

22-Sapphire I
February 11, 2019

Since you don't see any error messages, I would put some logger statements in the code, to verify that it is trying to send the email.

 

Ascherer17
16-Pearl
June 30, 2026

I’ve had this same issue with the “Notifications” entities as well.  Using the “SendMessage” service on my MailThing will work, but if I set up a Notification to trigger from an event, no email is sent.  I set up a subscription to log a message on the same event and it DOES log the message.  Our ThingWorx platform is configured as a HA cluster, currently running version 10.1.1, but this issue has been across multiple versions.

Performing a rolling restart of my individual server nodes seems to resolve the problem and the Notifications ARE triggered for a while, but eventually they stop working again.  I’m curious to know if more people have experienced this issue.

UPDATE: Performing the rolling restart (cycling nodes while platform remains up) is NOT working in today’s instance of this problem.  I believe it worked in the past but seemingly not today.  Maybe the problem has something to do with the cache/Ignite instances?