The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Hi all,
I am using a count to summarize the total events for specific objects within an hour bucket.
If there are no events for a specific object, I would like to trigger a powerautomate flow.
now designed it as such:
1) count (random attribute) 1 hour
2) becomes less than 1, stays for 1 hour
3) trigger flow.
But right now, I am receiving my triggers 1h late. I.e., no events between 5-6, i get a trigger at 7 that there were no events.
To my understanding, this happens as no logs where found between 5-6, so the condition became true at 6. Then stayed true until 7 (cuz it doesn't change due to 1 h buckets), hence it was 1 h late.
If I would change (2) to "becomes less than 1", wouldn't my triggers be sent every hour as they always start at 0 for a new hour bucket?
hope you can help, or point me in the right direction.
kind regards.
Kjell
Solved! Go to Solution.
Hi @kjellvs ,
For a more immediate response without the additional 1-hour delay, adjusting the condition to "becomes less than 1" is a viable solution. This change should allow the trigger to activate as soon as the condition is met (i.e., when the count becomes less than 1), without waiting for an additional hour.
Condition types fall into the following categories:
You can adjust the type of condition to suit your needs.
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @kjellvs ,
For a more immediate response without the additional 1-hour delay, adjusting the condition to "becomes less than 1" is a viable solution. This change should allow the trigger to activate as soon as the condition is met (i.e., when the count becomes less than 1), without waiting for an additional hour.
Condition types fall into the following categories:
You can adjust the type of condition to suit your needs.
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks, makes sense, but that also means that the summarization of 1 hour is only "materialized" (i.e., the value becomes applicable) at the end of the hour, if I am correct?
Hi @kjellvs ,
Becomes conditions activate only when the condition becomes true, after having previously been false. For example, “Becomes less than 1” will activate if the value of the property changes from a value of 2 (greater than 1) to a value of 0 (less than 1). It will only activate again when the condition goes from being false to true.
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
That makes sense, but when the hour jumps from the 2pm bucket to the 3pm, its starts at 0 in the 3 pm bucket. Then you could argue that the condition becomes true, as it went from e.g. 7 in the 2pm bucket, to 0 in the 3pm bucket. But the bucket just started, so I suppose the value is only considered at the end of the bucket?
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Fabric update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.