When the disk is full, ISM policy (rollover and delete) will fail

Versions (relevant - OpenSearch/Dashboard/Server OS/Browser):

2.9.1

Describe the issue:

When the disk is full, ISM policy (rollover and delete) will fail
the delete action will not be executed.
I need to know what to do to ensure that delete operations can be executed normally after the disk is full.
Configuration:

{
   "_id" : "logs-clean-policy",
   "_primary_term" : 1,
   "_seq_no" : 0,
   "_version" : 1,
   "policy" : {
      "default_state" : "normal_state",
      "description" : "Log index rollover and clean policy.",
      "error_notification" : null,
      "ism_template" : [
         {
            "index_patterns" : [
               "logs-*"
            ],
            "last_updated_time" : 1743234985928,
            "priority" : 100
         }
      ],
      "last_updated_time" : 1743234985928,
      "policy_id" : "logs-clean-policy",
      "schema_version" : 18,
      "states" : [
         {
            "actions" : [
               {
                  "retry" : {
                     "backoff" : "exponential",
                     "count" : 3,
                     "delay" : "1m"
                  },
                  "rollover" : {
                     "min_doc_count" : 2000000,
                     "min_index_age" : "1h",
                     "min_size" : "500mb"
                  }
               }
            ],
            "name" : "normal_state",
            "transitions" : [
               {
                  "conditions" : {
                     "min_index_age" : "7d"
                  },
                  "state_name" : "delete_state"
               }
            ]
         },
         {
            "actions" : [
               {
                  "delete" : {},
                  "retry" : {
                     "backoff" : "exponential",
                     "count" : 3,
                     "delay" : "1m"
                  }
               }
            ],
            "name" : "delete_state",
            "transitions" : []
         }
      ]
   }
}

Relevant Logs or Screenshots: