Snapshot management policy snapshoting failed without latest_execution.info field

Snapshot started to failed since 10 days, without any logs to help. Nothing changed concerning the SM policy configuration.

{
  "policies": [
    {
      "name": "snapshot-abc",
      "creation": {
        "current_state": "CREATION_START",
        "trigger": {
          "time": 1712253600000
        },
        "latest_execution": {
          "status": "FAILED",
          "start_time": 1712239399209,
          "end_time": null
        }
      },
      "deletion": {
        "current_state": "DELETION_START",
        "trigger": {
          "time": 1712286000000
        },
        "latest_execution": {
          "status": "FAILED",
          "start_time": 1712199799200,
          "end_time": null
        }
      },
      "policy_seq_no": 63243851,
      "policy_primary_term": 243,
      "enabled": true
    }
  ]
}

Any idea? My only guess is that the ism config is not triggered, due to this log

[2024-04-04T09:51:10,198][INFO ][o.o.j.s.JobSweeper       ] [es-main-master-1] Error while sweeping shard [.opendistro-ism-config][0], error message: all shards failed

But the shard status is green…

Any help would be appreciated!

I solved the error the hard way by deleting my index .opendistro-ism-configand reconfigure the sm policy. This action remove every ISM and co you could have configured until then (every action triggered by the JobScheduler). My intuition is that the JobScheduler couldn’t validate the configurations stored in the index .opendistro-ism-config. I guess that I could have clean it manually know that i know the issue is linked to it.