···11+---
22+'@urql/exchange-persisted': patch
33+---
44+55+Warn about cached persisted-miss results in development, when a `persistedExchange()` sees a persisted-miss error for a result that's already seen a persisted-miss error (i.e. two misses). This shouldn't happen unless something is caching persisted errors and we should warn about this appropriately.
···216216 retries.next(followupOperation);
217217 return null;
218218 } else if (result.error && isPersistedMiss(result.error)) {
219219+ if (result.operation.extensions.persistedQuery.miss) {
220220+ if (process.env.NODE_ENV !== 'production') {
221221+ console.warn(
222222+ 'persistedExchange()’s results include two misses for the same operation.\n' +
223223+ 'This is not expected as it means a persisted error has been delivered for a non-persisted query!\n' +
224224+ 'Another exchange with a cache may be delivering an outdated result. For example, a server-side ssrExchange() may be caching an errored result.\n' +
225225+ 'Try moving the persistedExchange() in past these exchanges, for example in front of your fetchExchange.'
226226+ );
227227+ }
228228+229229+ return result;
230230+ }
219231 // Update operation with unsupported attempt
220232 const followupOperation = makeOperation(
221233 result.operation.kind,