Delayed alert from Power BI to Teams - Fabric Activator

[KavibharathiS]

Recevied the Alert from Fabric Activator in Teams almost after 3 hours from the activated time which doesn't serves the purpose. Please help

[KavibharathiS]

Thanks Ibendlin. Pasting the response from Microsoft Fabric support.
It was mentioned that if there is a date/time column in the table that we created the alert on. This is a known issue, the alert may use the date/time column as the event timestamp instead of a system generated one. We have duplicate the column ans change the data type to Text and use or remove the date/time column and recreate the alert. The Alert was using the CET timestamp in UTC which created image of 3 hours delay.
Data Activator in Fabric has a built-in hourly check for trigger conditions, so it is expected for the alerts to have the delay of 1 hour to be received.

[v-priyankata]

Hi @KavibharathiS 
Thank you for sharing this information it will be helpful for others in the community facing similar issues. If you have any further questions or concerns, please reach out to the community.

[lbendlin]

Thank you for the update.  That makes this even more unfit for production. Hope they severely reconsider their design.

[v-priyankata]

Hi @KavibharathiS  

Thank you for reaching out to the Microsoft Fabric Forum Community. @lbendlin - Thanks for the inputs.
As said by user, I hope you have raised support ticket. If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thanks.

[lbendlin]

There is no SLA for the real-time-ness of Activator.  But yes, three hours is a bit excessive.

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .