Forum Discussion
Power BI Alert Activator - MaxDelayReached Error
Hi, I am getting the issue below for my alerts because it is not a consistent alert that occurs withing seven days. However, it is still an important alert that needs to be sent to stakeholders.
The error code means that Fabric Activator is unable to receive incoming data for your rule for the past seven days, and isn't evaluating your rule. It indicates an internal problem with Fabric Activator.
Hi UserBrendan ,
Your alert is tied to table visuals and only triggers when specific rows meet certain criteria. Data Activator treats these row updates as “incoming data.” When no new or updated data is received for over seven days, the rule becomes inactive, resulting in the MaxDelayReached message.
To avoid this, the most reliable solution is to ensure that Data Activator receives some form of data at least once every seven days even when the alert condition itself is not met. This keeps the rule active and able to evaluate future conditions.
A simple way to achieve this is to introduce a small “alert” update. You can schedule a query or pipeline via Power Query, SQL job, Fabric pipeline, Dataflow Gen2, etc. that sends a lightweight row such as:
LastUpdated = <today’s date>
Status = "alert"
This row won’t might trigger your alert but will keep the rule alive and prevent MaxDelayReached.
Hope this helps.
Thank you.
4 Replies
Hi, I am getting the issue below for my alerts because it is not a consistent alert that occurs withing seven days. However, it is still an important alert that needs to be sent to stakeholders.
What is the best way to resolve this issue, given that the alert is based on a table visual and uses specific columns from the designated table to apply criteria and return relevant rows for stakeholders?
MaxDelayReachedThe error code means that Fabric Activator is unable to receive incoming data for your rule for the past seven days, and isn't evaluating your rule. It indicates an internal problem with Fabric Activator.
Hi UserBrendan ,
Your alert is tied to table visuals and only triggers when specific rows meet certain criteria. Data Activator treats these row updates as “incoming data.” When no new or updated data is received for over seven days, the rule becomes inactive, resulting in the MaxDelayReached message.
To avoid this, the most reliable solution is to ensure that Data Activator receives some form of data at least once every seven days even when the alert condition itself is not met. This keeps the rule active and able to evaluate future conditions.
A simple way to achieve this is to introduce a small “alert” update. You can schedule a query or pipeline via Power Query, SQL job, Fabric pipeline, Dataflow Gen2, etc. that sends a lightweight row such as:
LastUpdated = <today’s date>
Status = "alert"
This row won’t might trigger your alert but will keep the rule alive and prevent MaxDelayReached.
Hope this helps.
Thank you.Hi UserBrendan ,
I just wanted to check if the issue has been resolved on your end, or if you require any further assistance. Please feel free to let us know, we’re happy to help!
Thank you
Chaithra E.Hi UserBrendan ,
May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.
Thank you.
