Totara Learn Open Discussions

Cette discussion de forum a été supprimée

 
Ce message du forum a été supprimé
Tuesday 22 October 2019, 13:28
Le contenu de ce message de forum a été supprimé et n'est plus accessible.
me
Re: Totars 12 Seminar notifications
par George Angus, Wednesday 23 October 2019, 12:42
Groupe Totara

Hi Will,

Which template are you using? Who is getting the duplicate emails? When do they get them?

cheers,

George.

Ce message du forum a été supprimé
Wednesday 23 October 2019, 13:26
Le contenu de ce message de forum a été supprimé et n'est plus accessible.
Holly Doggett
Re: Totara 12 Seminar notifications
par Holly Doggett, Friday 25 October 2019, 14:19
 

We are afraid what might be happening is that Totara is duplicating the event.

Each time we create an event, each attendee receives the built-in, pre-made Totara confirmation email that we have activated in the seminar notifications. Perfect.

But when it's time for the event reminder to go out (the pre-loaded, built-in Totara reminder), it goes twice, one minute apart, to every attendee. It also shows up twice in their notifications menu and also in the notifications screen in their account. They get 2 calendar items for the same event as well.

We have spent hours on this to no avail. What could be causing this? We only started receiving the complaints once we upgraded to Totara 12--we've been using the notifications for about a year now.

By the way: why do we have to choose "all events (past, present, future)" when we choose booked as the recipients for an event notification? Of course wait-listed and not booked people are not options for this notification. why can't we just choose "booked" and be done?

Thanks to any one who can provide insight! We're exhausted.




Ce message du forum a été supprimé
Monday 28 October 2019, 07:49
Le contenu de ce message de forum a été supprimé et n'est plus accessible.
Tom Wood
Re: Totara 12 Seminar notifications
par Tom Wood, Monday 28 October 2019, 14:48
Groupe Totara

Hi,

Thanks for reporting this issue. I can confirm that our development team are in the process of investigating this. We suspect these similar reports are related and we have a ticket open to track down the cause.

You can check for progress updates on the public tracker.

If we need more information to help us investigate the problem we'll let you know.

Thanks

Tom

Totara Product Support