You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/notifications.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,7 +130,7 @@ This example stops all notifications other than those for `User1`:
130
130
131
131
SQLMesh notifications are triggered by events. The events that should trigger a notification are specified in the notification target's `notify_on` field.
132
132
133
-
Notifications are supported for [`plan` application](../concepts/plans.md) start/end/failure, [`run`](../reference/cli.md#run) start/end/failure, and [`audit`](../concepts/audits.md) failures.
133
+
Notifications are supported for [`plan` application](../concepts/plans.md) start/end/failure, [`run`](../reference/cli.md#run) start/end/failure, and [`audit`](../concepts/audits.md)passes and failures.
134
134
135
135
For `plan` and `run` start/end, the target environment name is included in the notification message. For failures, the Python exception or error text is included in the notification message.
136
136
@@ -145,6 +145,7 @@ This table lists each event, its associated `notify_on` value, and its notificat
145
145
| SQLMesh run end | run_end | "SQLMesh run finished for environment `{environment}`." |
146
146
| SQLMesh run failure | run_failure | "Failed to run SQLMesh.\n{exception}" |
0 commit comments