# Failed migration of system indices (.triggered\_watches) with Upgrade Assistant using v7.17.14 **URL:** \ **Category:** Elasticsearch\ **Tags:** migration\ **Created:** [November 13, 2023, 8:32am UTC](https://discuss.elastic.co/t/failed-migration-of-system-indices-triggered-watches-with-upgrade-assistant-using-v7-17-14/346966 "2023-11-13T08:32:18Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![William\_Brafford](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/william_brafford/32/51559_2.png) [@William\_Brafford](https://discuss.elastic.co/u/William_Brafford)\ **Post date:** [November 27, 2023, 4:37pm UTC](https://discuss.elastic.co/t/failed-migration-of-system-indices-triggered-watches-with-upgrade-assistant-using-v7-17-14/346966/4 "2023-11-27T16:37:55Z")
Sorry for taking a long time to respond. I was on vacation. If you are still getting a message like this one, but with `.watches` instead of `.triggered_watches`, you can delete the > [@AEA27](#): > > `[instance-0000000013] task [upgrade-system-indices] failed with an exception java.lang.IllegalStateException: unable to create new index [.triggered_watches-reindexed-for-8] because it would match composable template [.triggered_watches]` You can [delete the index template](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-delete-template.html) without affecting the index at all. In this case, you'd have something like ```auto DELETE /_index_template/.watches,.triggered_watches ``` These templates were created before Elasticsearch had the "system index" feature, and Elasticsearch now uses a different internal mechanism to create settings and mappings for `.watches` and `.triggered_watches`. --- _[View the full topic](https://discuss.elastic.co/t/failed-migration-of-system-indices-triggered-watches-with-upgrade-assistant-using-v7-17-14/346966)._