elastic · JeremyDahlgren · May 23, 2025 · May 30, 2025 · May 30, 2025 · May 30, 2025
diff --git a/output/openapi/elasticsearch-openapi.json b/output/openapi/elasticsearch-openapi.json
diff --git a/output/schema/schema.json b/output/schema/schema.json
diff --git a/specification/snapshot/status/SnapshotStatusRequest.ts b/specification/snapshot/status/SnapshotStatusRequest.ts
@@ -30,6 +30,11 @@ import { Duration } from '@_types/Time'
  *
  * If you omit the `<snapshot>` request path parameter, the request retrieves information only for currently running snapshots.
  * This usage is preferred.
+ * Note that if a node has been restarted or has left the cluster since completing a shard snapshot the stats for that shard will be unavailable.
+ * Loading the stats from the repository is an expensive operation (see the WARNING below), so to minimize latency for returning stats for currently
+ * running snapshots the stats values will be -1 for these shards even though the "stage" value will be "DONE".  A "description" field will be set
+ * on these shard stats instances indicating why they are empty.  Note that the total stats for the index will be less than expected due to the
+ * missing values from these shards.
  * If needed, you can specify `<repository>` and `<snapshot>` to retrieve information for specific snapshots, even if they're not currently running.
  *
  * WARNING: Using the API to return the status of any snapshots other than currently running snapshots can be expensive.