topic Re: How to Make Data Activator Trigger Only Once Per Day Without Modifying Power BI? in Activator

How to Make Data Activator Trigger Only Once Per Day Without Modifying Power BI?

anushenoy — Fri, 14 Mar 2025 08:51:13 GMT

Hi Fabric Community,

We have a Power BI dashboard that tracks error counts, and we want to set up Data Activator to trigger an alert only once per day when errors occur. However, our Power BI dataset refreshes at irregular intervals, and Data Activator checks the dataset every 3600 seconds (1 hour) by default, which can cause multiple alerts.

We don’t want to modify the Power BI table (e.g., adding flags or timestamps) use Power Automate. Is there any setting in Data Activator itselft that allows us to limit the trigger frequency to only once per day?

Would adjusting “When it has been true for N times”, “Number of times”, help in ensuring only one alert is fired per day regardless of Power BI refresh timing?

Thanks in advance for your help!

Re: How to Make Data Activator Trigger Only Once Per Day Without Modifying Power BI?

lbendlin — Fri, 14 Mar 2025 12:17:42 GMT

Your requirement is incompatible with the idea of a trigger.

If you need a scheduled report, create a scheduled report.

Re: How to Make Data Activator Trigger Only Once Per Day Without Modifying Power BI?

Abdel19 — Fri, 25 Apr 2025 12:02:31 GMT

Hi, did you figure out how to fix this issue ?

Re: How to Make Data Activator Trigger Only Once Per Day Without Modifying Power BI?

v-priyankata — Mon, 02 Jun 2025 19:29:53 GMT

Hi anushenoy

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

Re: How to Make Data Activator Trigger Only Once Per Day Without Modifying Power BI?

anushenoy — Tue, 03 Jun 2025 07:46:18 GMT

✅ Resolved

Thanks for the suggestions! Just to clarify for anyone facing a similar issue - the solution wasn't based on adjusting the 3600-second trigger interval in Data Activator.

Instead, we handled it by enhancing the Power BI logic itself. We introduced conditions to check:

Whether a ticket already exists (to avoid duplicate alerts), and
Whether the dashboard refresh time in UTC had changed (to ensure alerts are only triggered once).

By combining these checks along with few more conditions in Power BI columns & then adding it to Activator, we were able to control the alert frequency effectively and ensure Data Activator only triggers as per need, regardless of how often the dataset refreshes.

Hope this helps others working through similar scenarios!