Did you create other indexes recently? If so, you must wait for that change to propagate to the rest of the search heads and indexers before creating another.
Are you working on an indexer cluster environment? I am asking because this error message is related with a cluster master issue when deploying a new bundle configuration.
If so, I would rollback the current configuration running this command from CLI
./splunk rollback cluster-bundle
Or using web - https://docs.splunk.com/Documentation/Splunk/8.0.2/Indexer/Updatepeerconfigurations#Rollback_the_con....
Restart the cluster master and Indexer cluster and try to redeploy the bundle.
please check this document for further information- > https://docs.splunk.com/Documentation/Splunk/8.0.2/Indexer/Updatepeerconfigurations
The question is tagged with splunk-cloud so no CLI is available.
This can happen when validation fails (for multiple reasons). If the indexes.conf your are trying to deploy has not changed, you'll never get a new bundle created. One workaround that I use for this issue is to simply modify indexes.conf, and a extra "space" to the file (so that it is different from previous version) and re-validate, then push it out again.
As this is cloud we do not have access to modify indexes.conf. Splunk vendor team has done the necessary changes and a rolling restart performed. Now we are able to see the new index created