Index showing wrong policy_seq_no

Following API is showing policy_seq_no as -2 … I believe it should show the _seq_no of attached policy. Whenever we modify the policy _seq_no gets change. It will help us to know which version of the policy is attached with instance.

GET _opendistro/_ism/explain/vikrant-000005

{
  "vikrant-000005" : {
    "index.plugins.index_state_management.policy_id" : "hot_warm_delete",
    "index.opendistro.index_state_management.policy_id" : "hot_warm_delete",
    "index" : "vikrant-000005",
    "index_uuid" : "F78p5ry2T0C7eJjN5WnzuA",
    "policy_id" : "hot_warm_delete",
    "policy_seq_no" : -2,
    "policy_primary_term" : 0,
    "rolled_over" : true,
    "index_creation_date" : 1653557536582,
    "state" : {
      "name" : "warm",
      "start_time" : 1653558783023
    },
    "action" : {
      "name" : "transition",
      "start_time" : 1653558783023,
      "index" : -1,
      "failed" : false,
      "consumed_retries" : 0,
      "last_retry_time" : 0
    },
    "step" : {
      "name" : "attempt_transition_step",
      "start_time" : 1653558783023,
      "step_status" : "condition_not_met"
    },
    "retry_info" : {
      "failed" : false,
      "consumed_retries" : 0
    },
    "info" : {
      "message" : "Evaluating transition conditions [index=vikrant-000005]"
    },
    "enabled" : true
  },
  "total_managed_indices" : 1
}

Using opensearch-1.3.2-1.x86_64 version.