Fabric Activator

Hi giselle ,

Thank you for reaching out to fabric community.

The issue is likely related to the timestamp / time-zone configuration and how the Activator rule evaluates the data. Please verify that the timestamp in the source data is in the expected time zone, especially if it is stored in UTC while you are viewing it in local time. Also, ensure the alert is evaluating the latest/current value, as Activator does not continuously re-evaluate already processed historical time points.

For the percentage value, 0.1 is the correct underlying value for 10%. Therefore, if your alert condition is intended to trigger at 10%, the threshold should generally be configured as 0.1, not 10.

I recommend checking the following:

• Verify the source timestamp and its time zone (UTC vs. local time).
• Confirm that the latest data point is being received by Activator.
• Check the alert condition and use 0.1 for 10%.
• Use the Rule Preview to confirm whether the condition is actually being met.
• If the condition is met but no notification is generated, check the action/execution history for the alert.

Thanks!!

Hi giselle​ ,

Could you check the suggestion provided above and let us know if you have any additional queries?

Thanks!!

Hi giselle​,

One thing in your screenshot makes me think the rule condition itself may already be working: the History tab shows 2 activations today.

I'd therefore separate the rule firing from the Teams action being delivered.

The time difference also may not be the issue by itself. Your chart is labelled Time (UTC), and Activator documents its ingestion timestamp in UTC, so an offset from your local time doesn't necessarily mean the data is arriving late. The Activator event model documentation explains the distinction between event time and ingestion time.

For the percentage, if % In Budget has an underlying value of 0.1 and is formatted as 10% in Power BI, then using 0.1 in the condition is correct. I would still verify the actual value arriving in Activator rather than relying only on the display format.

Since the rule has recorded activations, I'd try Send me a test action next. Microsoft documents this as a way to test the configured action using a past event that satisfied the condition: test an Activator rule.

If that test doesn't produce the Teams message, I'd focus on the action side. Microsoft's Activator troubleshooting guidance lists Teams-specific issues such as recipient problems, the Activator app being blocked in the tenant, or the bot being blocked.

So based on the screenshot, I would test the Teams action before changing the timestamp or threshold logic.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.

Hi giselle​ ,

Could you review the suggestion provided above and let us know if you have any additional questions, we are happy to address. 

Thanks!!