diff --git a/.generator/schemas/v1/openapi.yaml b/.generator/schemas/v1/openapi.yaml
index 050e782eb9c3..051a69bc0246 100644
--- a/.generator/schemas/v1/openapi.yaml
+++ b/.generator/schemas/v1/openapi.yaml
@@ -11815,7 +11815,8 @@ components:
         The default option results in different behavior depending on the monitor query type.
         For monitors using Count queries, an empty monitor evaluation is treated as 0 and is compared to the threshold conditions.
         For monitors using any query type other than Count, for example Gauge, Measure, or Rate, the monitor shows the last known status.
-        This option is only available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+        This option is available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+        It is also required for metric monitors that use `scheduling_options.custom_schedule`.
       enum:
         - "default"
         - "show_no_data"
diff --git a/lib/datadog_api_client/v1/models/monitor_options.rb b/lib/datadog_api_client/v1/models/monitor_options.rb
index 80bd2cf2fe98..da9c3a0c9e47 100644
--- a/lib/datadog_api_client/v1/models/monitor_options.rb
+++ b/lib/datadog_api_client/v1/models/monitor_options.rb
@@ -111,7 +111,8 @@ class MonitorOptions
     # The default option results in different behavior depending on the monitor query type.
     # For monitors using Count queries, an empty monitor evaluation is treated as 0 and is compared to the threshold conditions.
     # For monitors using any query type other than Count, for example Gauge, Measure, or Rate, the monitor shows the last known status.
-    # This option is only available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+    # This option is available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+    # It is also required for metric monitors that use `scheduling_options.custom_schedule`.
     attr_accessor :on_missing_data
 
     # The number of minutes after the last notification before a monitor re-notifies on the current status.
diff --git a/lib/datadog_api_client/v1/models/on_missing_data_option.rb b/lib/datadog_api_client/v1/models/on_missing_data_option.rb
index c70173672323..53a6b50b0c7c 100644
--- a/lib/datadog_api_client/v1/models/on_missing_data_option.rb
+++ b/lib/datadog_api_client/v1/models/on_missing_data_option.rb
@@ -21,7 +21,8 @@ module DatadogAPIClient::V1
   # The default option results in different behavior depending on the monitor query type.
   # For monitors using Count queries, an empty monitor evaluation is treated as 0 and is compared to the threshold conditions.
   # For monitors using any query type other than Count, for example Gauge, Measure, or Rate, the monitor shows the last known status.
-  # This option is only available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+  # This option is available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+  # It is also required for metric monitors that use `scheduling_options.custom_schedule`.
   class OnMissingDataOption
     include BaseEnumModel