# \#persisted-queries

**URL:** https://community.apollographql.com/tag/persisted-queries/39.md

[Latest](https://community.apollographql.com/latest.md) · [Categories](https://community.apollographql.com/categories.md) · [Tags](https://community.apollographql.com/tags.md)

---

## [Reviewing, approving and persisting queries to the safelist](https://community.apollographql.com/t/reviewing-approving-and-persisting-queries-to-the-safelist/9715)

<div class="topic-metadata">

**Author:** [@SusanPrice](https://community.apollographql.com/u/SusanPrice)\
**Replies:** 0\
**Last updated:** [February 11, 2026, 8:24pm UTC](https://community.apollographql.com/t/reviewing-approving-and-persisting-queries-to-the-safelist/9715 "2026-02-11T20:24:15Z")

</div>

For large enterprises with a federated graph (5+ subgraphs, 100+ consuming clients), can you share your process for reviewing, approving and persisting queries to the safelist?

---

## [Persisted Query List Management](https://community.apollographql.com/t/persisted-query-list-management/8743)

<div class="topic-metadata">

**Author:** [@jmccall](https://community.apollographql.com/u/jmccall)\
**Replies:** 2\
**Last updated:** [March 26, 2025, 5:35am UTC](https://community.apollographql.com/t/persisted-query-list-management/8743 "2025-03-26T05:35:48Z")

</div>

I started implementing persisted queries in our testing and production graphs. I realized a weakness to my approach - how do we properly prune this list over time when a query changes? Are they designed to grow indefinit…

---

## [Logging unknown operations for persisted queries should include the "operationName" field, or emit some metrics](https://community.apollographql.com/t/logging-unknown-operations-for-persisted-queries-should-include-the-operationname-field-or-emit-some-metrics/8606)

<div class="topic-metadata">

**Author:** [@jmccall](https://community.apollographql.com/u/jmccall)\
**Replies:** 4\
**Last updated:** [February 26, 2025, 9:57pm UTC](https://community.apollographql.com/t/logging-unknown-operations-for-persisted-queries-should-include-the-operationname-field-or-emit-some-metrics/8606 "2025-02-26T21:57:00Z")

</div>

Forgive me if this is the wrong place for this. Happy to make this a GH issue/feature request if that’s better. I’d like to start rolling out persisted queries on my supergraph, with an eye towards safe-listing them in …

---

## [Unknown logs in persisted query](https://community.apollographql.com/t/unknown-logs-in-persisted-query/8041)

<div class="topic-metadata">

**Author:** [@varun\_sharma](https://community.apollographql.com/u/varun_sharma)\
**Replies:** 0\
**Last updated:** [December 27, 2024, 5:36am UTC](https://community.apollographql.com/t/unknown-logs-in-persisted-query/8041 "2024-12-27T05:36:35Z")

</div>

Hi, I am trying to implement registered persisted query. when i am running a query which is not there in my PQL, with apq as enabled it is logging the query in router logs with error code “PersistedQueryNotFound” but whe…