---
title: "Get auto-tune status for a SQL warehouse"
method: GET
path: "/api/v1/databricks/warehouses/{warehouse_id}/auto-tune/status"
tags: ["DATABRICKS", "Databricks", "Databricks Warehouses"]
---

# Get auto-tune status for a SQL warehouse

`GET /api/v1/databricks/warehouses/{warehouse_id}/auto-tune/status`

## Request

- Base URL: `https://api.myaltimate.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.myaltimate.com/api/v1/databricks/warehouses/{warehouse_id}/auto-tune/status`
- Auth: one of:
  - HTTP bearer
  - HTTP bearer

Get the current auto-tune mode, backoff thresholds, active
recommendation, in-progress monitoring window, and most recent audit
event for a SQL warehouse — the FE detail page's Auto Tune panel.

## Path parameters

- `warehouse_id` string, required

## Query parameters

- `instance_id` integer, required: Tenant instance ID (workspace) the warehouse runs in
- `workspace_id` string, required: Required Databricks workspace_id. Scopes credential resolution to the correct workspace on multi-workspace tenants (defends against cross-workspace warehouse_id collisions) AND is the join key the ingestion cost-savings mart uses to attribute realized savings on (workspace_id, entity_id); an empty or mismatched value silently drops all actual savings for this warehouse.
- `navigationSource` string, nullable

## Headers

- `x-tenant` string, required

## Response `200`

Successful Response

- WarehouseAutoTuneStatusResponse: Response for ``GET /databricks/warehouses/{id}/auto-tune/status``. This is the FE's contract for the warehouse detail page's Auto Tune panel — every field is intentionally optional/nullable so a never-touched warehouse (no config row, no recommendation, no history) still returns a well-formed 200 rather than a 404.
  - `auto_tune_mode` 'enabled' | 'disabled', required
  - `backoff_configuration` WarehouseAutoTuneBackoffConfiguration: User-configured backoff thresholds for the 7-day post-apply monitor. Mirrors Snowflake's ``BackoffConfiguration`` shape (percentages, not raw ratios) but adds bounds validation Snowflake's never had — a threshold below 110% would trigger backoff on ordinary noise, and an absurdly high one (past 1000%) defeats the monitor's purpose entirely. Both default to 150 (allow up to 1.5x the baseline before treating it as a regression).
    - `max_latency_percentage` number: Backoff triggers when live p95 latency exceeds this percentage of the pre-apply baseline for the sustained-breach window.
    - `max_queue_time_percentage` number: Backoff triggers when live p95 queue time (cold-start + at-capacity) exceeds this percentage of the pre-apply baseline.
    - `trigger_action` 'rollback': What a backoff does. Always 'rollback' (step back to the last config that ran clean); any other stored value reads as 'rollback'.
  - `current_auto_stop_mins` integer, nullable: Live-read from Databricks; None on a read failure (never guessed).
  - `active_recommendation` WarehouseAutoTuneActiveRecommendation: The current actionable recommendation, if any.
    - `rk` string, required
    - `recommended_auto_stop_mins` integer, nullable
    - `created_on` string, date-time, required
  - `monitoring` WarehouseAutoTuneMonitoring: The 7-day post-apply monitoring window, if one is in progress or has produced a stabilized/backed-off value.
    - `applied_at` string, date-time, required
    - `window_ends_at` string, date-time, required
    - `stable_auto_stop_mins` integer, nullable
    - `last_bad_auto_stop_mins` integer, nullable
  - `last_event` WarehouseAutoTuneLastEvent: The most recent audit event for this warehouse, for a lightweight "last changed" display without a full audit-history fetch.
    - `event_type` string, required
    - `change_timestamp` string, date-time, required
  - `preflight` WarehouseAutoTuneEnablePreflight: Whether the SP can currently enable auto-tune on this warehouse. Surfaced on the status response so the FE can render the Auto Tune Switch disabled with a persistent reason (instead of a momentary toast on a failed enable) when the service principal lacks CAN_MANAGE. Fail-open: any credential/read/timeout error leaves ``blocked=False`` (the hard enable-gate in the toggle path still protects the mutation). Used in two positions. Top-level it is the AUTO STOP axis's own enable gate: CAN_MANAGE is folded in, plus Auto Stop's ``no_active_recommendation``. It does not speak for Warehouse Sizing. ``can_manage_blocked`` is the only warehouse-wide half: when true the SP cannot edit this warehouse at all, so no axis can be enabled. A top-level ``blocked`` with ``can_manage_blocked`` false only means Auto Stop has nothing to apply; Warehouse Sizing may still be enableable. Each axis block's ``enable_preflight`` is that axis's own gate.
    - `blocked` boolean
    - `reason` string, nullable
    - `actionable_message` string, nullable
    - `can_manage_blocked` boolean
    - `turn_off_allowed` boolean
  - `pending_apply` boolean
  - `resize` WarehouseAutoTuneAxisStatus: One non-auto-terminate axis's status block. No current_auto_stop_mins — that is warehouse-level and stays top-level only. ``enable_preflight`` IS axis-level: each axis is enableable only while it has something to apply, so the gate has to be reported per axis rather than folded into the warehouse-level preflight.
    - `auto_tune_mode` 'enabled' | 'disabled', required
    - `backoff_configuration` WarehouseAutoTuneBackoffConfiguration: User-configured backoff thresholds for the 7-day post-apply monitor. Mirrors Snowflake's ``BackoffConfiguration`` shape (percentages, not raw ratios) but adds bounds validation Snowflake's never had — a threshold below 110% would trigger backoff on ordinary noise, and an absurdly high one (past 1000%) defeats the monitor's purpose entirely. Both default to 150 (allow up to 1.5x the baseline before treating it as a regression).
      - `max_latency_percentage` number: Backoff triggers when live p95 latency exceeds this percentage of the pre-apply baseline for the sustained-breach window.
      - `max_queue_time_percentage` number: Backoff triggers when live p95 queue time (cold-start + at-capacity) exceeds this percentage of the pre-apply baseline.
      - `trigger_action` 'rollback': What a backoff does. Always 'rollback' (step back to the last config that ran clean); any other stored value reads as 'rollback'.
    - `current_value` unknown
    - `active_recommendation` WarehouseAutoTuneAxisActiveRecommendation: Axis-generic active recommendation for a NON-auto-terminate axis. Deliberately not WarehouseAutoTuneActiveRecommendation: that class's field is named recommended_auto_stop_mins (int), which cannot also hold a resize axis's cluster_size (an ordinal string).
      - `rk` string, required
      - `recommended_value` unknown
      - `current_value` unknown
      - `created_on` string, date-time, required
      - `customer_reasoning` string, nullable
    - `monitoring` WarehouseAutoTuneAxisMonitoring: Axis-generic counterpart to WarehouseAutoTuneMonitoring — same shape, generic field names so a resize cluster_size string and an auto-terminate auto_stop_mins int both fit.
      - `applied_at` string, date-time, required
      - `window_ends_at` string, date-time, required
      - `stable_value` unknown
      - `last_bad_value` unknown
    - `last_event` WarehouseAutoTuneLastEvent: The most recent audit event for this warehouse, for a lightweight "last changed" display without a full audit-history fetch.
      - `event_type` string, required
      - `change_timestamp` string, date-time, required
    - `pending_apply` boolean
    - `enable_preflight` WarehouseAutoTuneEnablePreflight: Whether the SP can currently enable auto-tune on this warehouse. Surfaced on the status response so the FE can render the Auto Tune Switch disabled with a persistent reason (instead of a momentary toast on a failed enable) when the service principal lacks CAN_MANAGE. Fail-open: any credential/read/timeout error leaves ``blocked=False`` (the hard enable-gate in the toggle path still protects the mutation). Used in two positions. Top-level it is the AUTO STOP axis's own enable gate: CAN_MANAGE is folded in, plus Auto Stop's ``no_active_recommendation``. It does not speak for Warehouse Sizing. ``can_manage_blocked`` is the only warehouse-wide half: when true the SP cannot edit this warehouse at all, so no axis can be enabled. A top-level ``blocked`` with ``can_manage_blocked`` false only means Auto Stop has nothing to apply; Warehouse Sizing may still be enableable. Each axis block's ``enable_preflight`` is that axis's own gate.
      - `blocked` boolean
      - `reason` string, nullable
      - `actionable_message` string, nullable
      - `can_manage_blocked` boolean
      - `turn_off_allowed` boolean
  - `axis_flags` object, nullable
  - `annualized_cost_savings_usd` number, nullable
  - `realized_savings_usd` number, nullable
  - `additional_potential_savings_usd_per_month` number, nullable

## Other responses

- `403`: Not authorized
- `404`: Warehouse not found
- `422`: Validation Error

## Changes

- **2026-10-30** `77a7dface13f`: 1 info
  - added the non-success response with the status `404`
- **2026-10-14** `1b2d675195d7`: 2 info
  - added the optional property `preflight/turn_off_allowed` to the response with the `200` status
  - added the optional property `resize/anyOf[subschema #1: WarehouseAutoTuneAxisStatus]/enable_preflight/anyOf[subschema #1: WarehouseAutoTuneEnablePreflight]/turn_off_allowed` to the response with the `200` status
- **2026-10-07** `b4beb9e80982`: 1 info
  - added the optional property `resize/anyOf[subschema #1: WarehouseAutoTuneAxisStatus]/active_recommendation/anyOf[subschema #1: WarehouseAutoTuneAxisActiveRecommendation]/customer_reasoning` to the response with the `200` status
- **2026-09-30** `a1870d258a3a`: 6 info
  - the `trigger_action` response property const value `rollback` was added for the status `200`
  - the `trigger_action` response property const value `rollback` was added for the status `200`
  - the `trigger_action` response's property default value `rollback` was added for the status `200`
  - the `trigger_action` response's property default value `rollback` was added for the status `200`
  - …2 more
- **2026-09-23** `eebfc2f234e1`: 2 info
  - added the optional property `preflight/can_manage_blocked` to the response with the `200` status
  - added the optional property `resize/anyOf[subschema #1: WarehouseAutoTuneAxisStatus]/enable_preflight` to the response with the `200` status

[Operation history](https://skmtc.dev/myaltimate/apis/myaltimate-api/changes/api/v1/databricks/warehouses/:warehouse_id/auto-tune/status/get.md)

---

[API](https://skmtc.dev/myaltimate/apis/myaltimate-api.md) - [All operations](https://skmtc.dev/myaltimate/apis/myaltimate-api/llms.txt) - [OpenAPI document](https://skmtc.dev/myaltimate/apis/myaltimate-api/revisions/727657ce54e9?raw)