Kibana Data View field cache invalidation after Elasticsearch mapping revert

Kibana Data Views store field metadata derived from Elasticsearch mappings. When a mapping is reverted through an Index Template or the mapping API during a deployment rollback, the Data View field list may retain stale type definitions until the cache is refreshed.

The goal is to determine whether Kibana automatically invalidates this field cache when the underlying schema changes, or whether an operator must trigger a manual refresh after every schema-level revert.

Does the Data View API detect mapping reverts and refresh field metadata automatically? If not, which API call or UI action forces Kibana to reload field types from Elasticsearch without recreating the Data View?