*`query`: GraphQL query to fetch, specified using a`graphql` template literal, or a preloadable concrete request, which can be acquired by requiring the file`<name-of-query>$Parameters.graphql`. Relay will only generate the`$Parameters` file if the query is annotated with`@preloadable`.

*`variables`: Object containing the variable values to fetch the query. These variables need to match GraphQL variables declared inside the query.

*`options`:*_[Optional]_* options object

*`fetchPolicy`: Determines if cached data should be used, and whether to send a network request based on the cached data that is currently available in the Relay store (for more details, see our[Fetch Policies](../../guided-tour/reusing-cached-data/fetch-policies) and[Garbage Collection](../../guided-tour/reusing-cached-data/availability-of-data) guides):

*`fetchPolicy`: Determines if cached data should be used, and whether to send a network request based on the cached data that is currently available in the Relay store (for more details, see our[Fetch Policies](../../guided-tour/reusing-cached-data/fetch-policies) and[Garbage Collection](../../guided-tour/reusing-cached-data/presence-of-data) guides):

* "store-or-network":**(default)***will* reuse locally cached data and will*only* send a network request if any data for the query is missing. If the query is fully cached, a network request will*not* be made.

* "store-and-network":*will* reuse locally cached data and will*always* send a network request, regardless of whether any data was missing from the local cache or not.

* "network-only":*will not* reuse locally cached data, and will*always* send a network request to fetch the query, ignoring any data that might be locally cached in Relay.

*`fetchQuery` will automatically save the fetched data to the in-memory Relay store, and notify any components subscribed to the relevant data.

*`fetchQuery` will**NOT** retain the data for the query, meaning that it is not guaranteed that the data will remain saved in the Relay store at any point after the request completes. If you wish to make sure that the data is retained outside of the scope of the request, you need to call`environment.retain()` directly on the query to ensure it doesn't get deleted. See our section on[Controlling Relay's GC Policy](../../guided-tour/reusing-cached-data/availability-of-data) for more details.

*`fetchQuery` will**NOT** retain the data for the query, meaning that it is not guaranteed that the data will remain saved in the Relay store at any point after the request completes. If you wish to make sure that the data is retained outside of the scope of the request, you need to call`environment.retain()` directly on the query to ensure it doesn't get deleted. See our section on[Controlling Relay's GC Policy](../../guided-tour/reusing-cached-data/presence-of-data) for more details.

*`fetchQuery` will automatically de-dupe identical network requests (same query and variables) that are in flight at the same time, and that were initiated with`fetchQuery`.

import FbRefetchingQueriesUsingUseQueryLoader from './fb/FbRefetchingQueriesUsingUseQueryLoader.md';

import FbRefetchingQueriesUsingUseLazyLoadQuery from './fb/FbRefetchingQueriesUsingUseLazyLoadQuery.md';

import FbAvoidSuspenseCaution from './fb/FbAvoidSuspenseCaution.md';

import OssAvoidSuspenseNote from './OssAvoidSuspenseNote.md';

When referring to**"refetching a query"**, we mean fetching the query again for*different* data than was originally rendered by the query. For example, this might be to change a currently selected item, to render a different list of items than the one being shown, or more generally to transition the currently rendered content to show new or different content.

```js

```js

import FbRefreshingQueriesUsingUseQueryLoader from './fb/FbRefreshingQueriesUsingUseQueryLoader.md';

import FbAvoidSuspenseCaution from './fb/FbAvoidSuspenseCaution.md';

import FbRefreshingQueriesUsingUseLazyLoadQuery from './fb/FbRefreshingQueriesUsingUseLazyLoadQuery.md';

import OssAvoidSuspenseNote from './OssAvoidSuspenseNote.md';

When referring to**"refreshing a query"**, we mean fetching the*exact* same data that was originally rendered by the query, in order to get the most up-to-date version of that data from the server.

```js

The provided`fetchPolicy` will determine:

**whether* the query should be fulfilled from the local cache, and

**whether* a network request should be made to fetch the query from the server, depending on the[availability of the data for that query in the store](../availability-of-data/).

**whether* a network request should be made to fetch the query from the server, depending on the availability of the data for that query in the store.

By default, Relay will try to read the query from the local cache; if any piece of data for that query is[missing](../presence-of-data/) or[stale](../staleness-of-data/), it will fetch the entire query from the network. This default`fetchPolicy` is called "*store-or-network".*