offlineExchange and non-optimistic requests

[bigescalade]

Hello, we are using the offlineExchange to handle some optimistic mutations. This part works fine however when the device is offline and we attempt to query our graph the operation never completes and we receive no network error or timeout of any kind.

The docs read:

A similar mechanism is applied to optimistic mutations when the user is offline. Normal non-optimistic mutations are executed as usual and may fail with a network error. Optimistic mutations however will be queued up and may be retried when the app is restarted or when the user comes back online.

I know it says mutation but does it also apply to queries? should queries while offline fail with a network error?

EDIT:

just went through the docs again and found this:

When a query fails with a Network Error, which indicates that the client is offline — either because navigator.onLine is false or because the error message indicates an offline error — the offlineExchange won't deliver the error for this query to avoid it from being surfaced to the user. This works particularly well in combination with "Schema Awareness" which will deliver as much of a partial query result as possible. In combination with the cache-and-network request policy we can now ensure that we display as much data as possible when the user is offline while still keeping the cache up-to-date when the user is online.

so does that mean queries offline won't bubble up a network error?