Make sure your Scenario is enabled and running by browsing ScenarioManager component in dynamo admin's component browser.
Refer following link for details:
If your scenario in running then try enabling logging debug and ScenarioManager and see if you find something fishy in logs
Thanks for the answers. Logging debug helped me to solve the problem, I modified the scenario passing the siteId to the condition.
But now something a little strange is happening: sometimes the scenario sends the email, sometimes it doesn't do this.
And when scenario doesn't send the email, no logDebug and no erros are found.
Some help to solve this strange point?
Thanks in advance
Can you try by adding a time element between the register event and send email action. When a user registers, ATG internally uses some messages to update the system. To ensure that messages have been processed it is a good idea to wait for some time (say 5 minutes) after the register event in a scenario before taking the next action. See if it helps in your case.
I tried it, but the problem still happens. I did a new register, 5 minutes passed and the email was sent.
After it, I did another test, and after 5 minutes the email was not sent, but when I confirmed the new register the debug logs an event type Register was found and scenario has to send and email after 5 minutes. But not sent.
Any other idea?
I really don't know what are happening, I read many Oracle ATG docs and couldn't find any solution.
Not sure what exactly is the issue in your environment but just throwing in some ideas... TemplateEmailSender has a property to send emails in the same thread. You can check that as I think for local scenario events it can be safely set to false.
Try setting dummyMode to true in SMTPEmail and check whether you can see all of your email template's markup rendered in the console/server logs every time email action is triggered. I'm suggesting this just to confirm that email action is getting triggered after every registration event so we are good till that stage. Sometimes if you have more than one ATG instance connecting to same database, there is a possibility a rogue instance (which might have been registered as GSS/PES) can pull the JMS messages out of the internal event queue before a legitimate server gets it. So ensure that you are not running in this type of situation.
In ATG, when emails are sent using template email sender, a HTTP request is generated and serviced to render the email template JSP. So another area you may want to look at is if there is any custom pipeline servlet which is causing some issue as that request goes through the pipeline.