Hey @jathin12,
I’m guessing you used the “state” option in the API… this is a lack of documentation issue, I’m going to work with the technical writers to update it.
That “state” option lets you set the state the managed index should start in after the change policy takes affect. So if you had put “state”: “hot” then after the change policy happens it would move them all to the start of hot.
So immediate way to fix. Remove all your policies from affect indices. They will of course be in different lifecycles, so you need to create some temporary policies and reapply them to the indices. Temporary in the sense that they start in a start on the action where they left off from.
Edit: I have created a PR here: Updates ISM change policy API docs by dbbaughe · Pull Request #395 · opendistro/for-elasticsearch-docs · GitHub
Let me know if this clears up the API for you or if you think it needs more changes.