topic Re: Alert not working in Activator

Alert not working

apatnola — Wed, 14 Aug 2024 18:41:40 GMT

I have created an alert on a card that contains the count of ID.

Here is the rule. I have not received any notifications. The dataset has Row level security applied and I have a power bi desktop pro license. The workspace it is published in is a premium workspace. The dataset has refreshed daily since Aug 9 2024 with no notifications sent. I have refreshed again this afternoon and nothing.

The card has been greater than zero every day:

Re: Alert not working

apatnola — Wed, 14 Aug 2024 21:36:25 GMT

fyi, i created a second alter where the count of cycle_ID is greater than or equal to 10 and it works fine. But it is the one above I need to get working.

Re: Alert not working

Anonymous — Thu, 15 Aug 2024 07:25:02 GMT

Hi apatnola

First of all, I need to confirm with you what is the Detect setting in the following screenshot? According to the screenshot you provided, you set it to trigger every time it is greater than 0. But according to your second screenshot, your data is greater than 0 at all times. Does that mean it is in a triggered state every second? If so, you may need to try to reduce the number of trigger operations to see if the problem still exists.

You can also check if the following error is reported.

For more details, you can read related document link:

https://learn.microsoft.com/en-us/fabric/data-activator/data-activator-limitations#maximum-number-of-trigger-actions

https://learn.microsoft.com/en-us/fabric/data-activator/data-activator-troubleshooting#processinglimitsreached

Best Regards,
Yulia Xu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: Alert not working

apatnola — Mon, 19 Aug 2024 17:21:13 GMT

So, the card tells how many cycle counts were started prior to yesterday. It's a check designed to let managers know when they have a cycle count tying up inventory that needs attention. One of the reasons, it's always greater than 1 is that we do not have such an alert in place today and this is flying "under the radar". The data set has RLS applied so that managers only see the operating units they are responsible for. So, those that do not have aged open cycle counts shouldn't get anything and those that do should receive a daily alert until they complete or cancel the cycle count.

How do I reduce the number of events per second I'm sending to the object?

Re: Alert not working

apatnola — Mon, 19 Aug 2024 17:27:51 GMT

I went into the alert tab and reduced the range under events from all 24 hours to just 30 minutes:

Will that work?