The reason the alert is not functioning as expected is becauseDatabricks SQL Alerts do not support query parameters. This limitation applies to all types of parameters, including date parameters.

Here’s why:

Alerts require static, deterministic query resultsso they can compare values consistently during scheduled executions.

When a query includes parameters (e.g., a date range parameter), its results may change based on user input or the default value set in the query editor.

However,Databricks SQL Alerts will always use the default value set for the parameter at the time the alert is created. This means the alert doesn’t dynamically adapt to new date ranges and will not reflect changes unless the query is manually updated.

As a result, if the business logic behind the alert depends on changing date ranges or any user input, the alert will not trigger correctly, or may never trigger at all.

Therefore, the correct explanation contradictsOption B, which is incorrect in saying that alerts cannot work with date-based queries at all. In fact, theycan—as long as the query is static(i.e., without parameters).