Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

A new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.

Reply
Mauro89
Super User
Super User

Trigger activator action only if condition is met over certain time period

Hi there,

 

Iam searching for a possibility to only trigger a action with the activator if the condition is met once and then only lets say after an hour and if the condition is met again.

 

Example: I want to get a Teams message if my capacity exeeds 95% of interactive delay limit. And I dont want to get this message every time this condition is met, but only for example if the condition holds and then checking again after x amount of time.

 

Any ideas?

 

Thanks and best regards!

1 ACCEPTED SOLUTION
lbendlin
Super User
Super User

Use Power Automate instead and implement your own debouncer algorithm.

View solution in original post

4 REPLIES 4
lbendlin
Super User
Super User

Use Power Automate instead and implement your own debouncer algorithm.

@lbendlinthats possible of course. But I don't and to leave Fabric for such a easy rule. And I remember when Activator was in preview this feature was present somewhen. Iam curious if it jut went somewhere else or get dropped. 

Hi @Mauro89,

 

Thank you for reaching out to Microsoft Fabric Community.

 

Thank you @lbendlin for the prompt response. 

 

Here the activator can fire alerts based on a condition, but it does not have a built-in option to wait for a specific time before sending the next alert. It will either fire on every evaluation or only when the value moves into a new state.

If you need something like send the alert once and only send it again after x amount of time if the condition is still true, then the practical way is to trigger a small Power Automate flow from Activator. This keeps everything inside fabric and the flow can easily check when the last alert was sent and only send another message if the cooldown time is finished.

 

Thanks and regards,

Anjan Kumar Chippa

Thanks @lbendlin and @v-achippa this is a possible workaround. But as I would like to see this kind of condition as well in Fabric as this is a very common analysis pattern not only for capacity analysis it would be great to have it in Fabric. For that, I have created a idea here.

Feel free to give some kudos 😉

Helpful resources

Announcements
June Fabric Update Carousel

Fabric Monthly Update - June 2026

Check out the June 2026 Fabric update to learn about new features.

Fabric SQL PBI Data Days

Data Days 2026 coming soon!

Sign up to receive a private message when registration opens and key events begin.

New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Top Solution Authors