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
{{ message }}
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
If a job gets launched and something is wrong with it (example: the setup script has a syntax error), then the task is marked as failed and the error is recorded.
When jobs are launched via CICD, users have no way to know their jobs have failed. It would be good to provide a notification for these failures.
(Suggestion: Teams message)
The text was updated successfully, but these errors were encountered:
For the time being, webhook events with user information will be our default method to enable customized notification schemes. These features are merged into main, and will be in the next release.
Users can use services like Azure Logic Apps, to wire in these event based webhooks into arbitrary 3rd party services, including Outlook 365, ICM, Teams, Slack, Twillo, and more.
If a job gets launched and something is wrong with it (example: the setup script has a syntax error), then the task is marked as failed and the error is recorded.
When jobs are launched via CICD, users have no way to know their jobs have failed. It would be good to provide a notification for these failures.
(Suggestion: Teams message)
The text was updated successfully, but these errors were encountered: