Hi @Eliza_geo ,

Given your Unity Catalog + serverless + DABS environment, here's what makes sense right now:

For new pipelines: Stick to legacy SQL alerts invoked via a SQL task in Jobs. Avoid the SQL Alert task (Beta) in production workflows — Beta features can have breaking changes between releases.
For DABS management of alerts: Use the legacy Alerts API (/api/2.0/preview/sql/alerts) directly in a notebook or Python task within your job to create/manage alerts programmatically, since DABS + V2 alert + SQL task is a broken triangle right now.
Watch the release notes: The Databricks release notes are updated frequently. 
Flag it with your account team: If this is blocking a production design decision, your Databricks TAM or AE can give you a non-public roadmap signal i think.