Asset Bundles: How to mute job failure notifications until final retry?

[arendon]

I'm trying to configure a job to only send failure notifications on the final retry failure (not on intermediate retry failures). This feature is available in the Databricks UI as "Mute notifications until the last retry", but I can't get this to work through the YAML configuration using Asset Bundles. I've tried to include mute_notifications_until_the_last_retry: true, which generates "unknown field" warnings during bundle deployment.

Is this setting supported in Asset Bundles? If not, are there any workarounds to achieve "notify only on final failure" behavior using bundle configurations? Once deployed via Asset Bundles, any attempt to edit the settings within the UI shows "Modify bundle sources and redeploy to edit this job", so manual configuration isn't possible.

Any guidance would be greatly appreciated!

[lingareddy_Alva · Accepted solution]

Hi @arendon 

The mute_notifications_until_the_last_retry field you're trying to use isn't currently supported in Databricks Asset Bundles YAML configuration,
which explains why you're getting the "unknown field" warnings.
This is a common issue where certain UI features haven't been fully exposed through the programmatic configuration options yet.
Here are a few approaches you can try:

Workarounds
1. Use Terraform Provider Instead
If you're open to using Terraform instead of or alongside Asset Bundles,
the Databricks Terraform provider often has more complete field coverage.

2. Post-Deployment API Call
You could deploy your bundle and then make a direct API call to update the notification settings.

3. Check Alternative Field Names
Sometimes the YAML field names differ from the UI labels. Try these variations in your bundle configuration.

4. File a Feature Request
Since this is a gap between UI capabilities and Asset Bundle support, consider filing a feature request with Databricks
support to add this field to the Asset Bundle schema.

Verification Steps
To check what notification fields are currently supported in your Asset Bundle version, you can:
1. Run databricks bundle schema to see available fields
2. Check the latest Databricks Asset Bundle documentation
3. Look at the job resource schema specifically.

[arendon]

Thank you for the response, @lingareddy_Alva!

I'll take a look at the workarounds you shared.