Page 1 of 1

Event Listener sends email three times

Posted: Thu Oct 12, 2017 4:42 pm
by pro7
Hi,
We setup an event listener to send an email when a graph gets an error. For some reason the email is sent three times. I don't see anything in the event listener that would cause this. There is only one email address defined. Any ideas??

Thanks,
pro7

Re: Event Listener sends email three times

Posted: Tue Oct 17, 2017 3:06 pm
by bartonv
Hi Pro7,
I would suggest reviewing the following settings in order to narrow the issue down:
  • Check the setup of the Event Listener, specifically the CC, Bcc and Reply-to section (which is hidden by default). Make sure that the email address in question is indeed listed only once.
  • Is the email address referenced in its absolute form ([email protected]) or by a parameter ${user.email}? If the latter is the case, you might want to review the user setup in the server console for the same reason (Configuration > Users > Edit User > E-mail).
  • Can you confirm that the 3 emails are indeed identical (as opposed to representing 3 different runs of the graph that failed 3 times in a row)?
If none of the above ideas helped you pinpoint the problem, feel free to get back to us with the following details:
  1. Is it graph event listener or jobflow event listener we are talking about? In other words, do you execute the graph itself or do you execute a jobflow containing an ExecuteGraph component?
  2. How do you start the graph/jobflow? It is scheduled to run a regular basis? Is it triggered by another event listener? Or is it run manually? If it is run manually, do you run it from the console or from the Designer?
  3. Which version of the CloverETL Designer and Server are you using?
  4. Is it happening to all your event listeners or only a specific one?
  5. Please also send us the respective run log and task detail (Task History > Actions column > Detail button).
Regards,

Re: Event Listener sends email three times

Posted: Tue Oct 17, 2017 3:33 pm
by pro7
Please disregard. I found the issue. Thanks

pro7