When the number of shards reaches 1000, ISM stops rollover indices. Even after I delete some shards, it still does not automatically resume rollover

OpenSearch
1

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

Describe the issue:

ism explain shows:

   ".ds-XXXXX-XXXX-000395" : {
      "action" : {
         "consumed_retries" : 3,
         "failed" : true,
         "index" : 0,
         "name" : "rollover",
      },
      "enabled" : false,
      "index" : ".ds-XXXXX-XXXX-000395",
      "info" : {
         "cause" : "Validation Failed: 1: this action would add [4] total shards, but this cluster currently has [998]/[1000] maximum shards open;",
         "message" : "Failed to rollover index [index=.ds-XXXXX-XXXX-000395]"
      },

I want the rollover to happen automatically after some shards are deleted. How can I achieve this?
Currently, even after deleting some shards, the rollover does not resume because the ‘enable’ setting is set to false.

Configuration:

    "states": [
      {
        "name": "normal_state",
        "actions": [
          {
            "retry": {
              "count": 3,
              "backoff": "exponential",
              "delay": "1m"
            },
            "rollover": {
              "min_index_age": "12h"
            }
          }
        ],
        "transitions": [
          {
            "state_name":"delete_state",
            "conditions": {
              "min_index_age": "7d"
            }
          }
        ]
      },

Relevant Logs or Screenshots:

2

I don’t think there is a way to achieve this, you would just need to make sure that it never reaches the limit, by either reducing the number of shards or increasing the limit:

PUT _cluster/settings
{
   "persistent":{
      "cluster.max_shards_per_node": 1500
   }
}