# Is my ILM policy stuck?
**URL:** https://discuss.elastic.co/t/is-my-ilm-policy-stuck/326543
**Category:** Elasticsearch
**Tags:** ilm-index-lifecycle-management
**Created:** [February 27, 2023, 6:36am UTC](https://discuss.elastic.co/t/is-my-ilm-policy-stuck/326543 "2023-02-27T06:36:44Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Shalinicts](https://discuss.elastic.co/u/Shalinicts)
#### Post date: [February 27, 2023, 6:36am UTC](https://discuss.elastic.co/t/is-my-ilm-policy-stuck/326543/1 "2023-02-27T06:36:44Z")
Hi Team ,
I have set my ILM policy to move from hot to frozen node when it reach 45 GB size in primary shard. Howver it is not yet moved and not showing any errors.
But if I do `Preformatted text`GET /metricbeat-\*/\_ilm/explain `Preformatted text`I get response like this :
````auto
"metricbeat-aws-pp-win-log-2023.01.07-000044" : {
"index" : "metricbeat-aws-pp-win-log-2023.01.07-000044",
"managed" : true,
"policy" : "metricbeat",
"lifecycle_date_millis" : 1673054181926,
"age" : "51.21d",
"phase" : "hot",
"phase_time_millis" : 1673054182799,
"action" : "rollover",
"action_time_millis" : 1673054183814,
"step" : "check-rollover-ready",
"step_time_millis" : 1673054183814,
"phase_execution" : {
"policy" : "metricbeat",
"phase_definition" : {
"min_age" : "0ms",
"actions" : {
"rollover" : {
"max_primary_shard_size" : "45gb"
},
"set_priority" : {
"priority" : 100
}
}
},
"version" : 8,
"modified_date_in_millis" : 1677403610454
}
},
```"
What does this mean . Is the ILM is stiull working ?
````
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 27, 2023, 6:37am UTC](https://discuss.elastic.co/t/is-my-ilm-policy-stuck/326543/2 "2023-03-27T06:37:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.