Expand my Community achievements bar.

Adobe Analytics Alerts: To be able to disable alerts without Adobe wiping the recipients list

Avatar

Level 2

8/8/22

Description - It appears that the way Adobe Analytics disables the alerts is to wipe the recipients list, re-enabling the alert means re-entering the list of recipients, can't work out if this is by design or a bug?

Why is this feature important to you - I don't want to have to enter all the recipients again if I choose to enable a saved alert I've previously disabled

How would you like the feature to work -  Disabling the alert should suppress the alert without deleting the list of recipients, when I enable the alert I shouldn't have to do anything else.

Current Behaviour - I have to re-enter recipients into my alert and save again

 

ellis_d82_1-1659966167320.png

 

 

ellis_d82_0-1659965986823.png

 

5 Comments

Avatar

Community Advisor

8/8/22

Totally agree on this one! You may need to temporarily disable an alert cause there was a bad code release and now the alert is triggered every time and it's spamming users...  but once the fix is deployed, you want to re-enable it.... not having to manually enter all the users one by one should be a no-brainer.

Avatar

Level 1

12/21/22

I also ran into this. You create alerts to know when you have an issue. But while the issue exists you don't need to keep getting alerts which means you want to disable them. But when you disable alerts it can remove all the recipients.

 

I've also found it's inconsistent. Some of my alerts had the recipient disabled. But some of them were fine. I'll pay more attention to this the next time I need to disable.

 

Adobe should at least review this and response. I'm going to create a ticket for it.

Avatar

Level 1

2/6/23

@ellis_d82 @Jennifer_Dungan I opened a ticket for this issue some time back. Engineering confirmed there was a problem but does not have a date for resolution. I will post here when I get more.

Avatar

Level 1

2/21/23

@ellis_d82 @Jennifer_Dungan Adobe tells me the fix for this is now in production. I do not plan to test this and will just see what happens when disable and re-enable an alert in the future.