Can revalidation be disabled when an error is thrown?

[alvvaro]

In my application, users can navigate to /item/[itemCode], and SWR will fetch the data related to that item. In cases where the item does not exist, the API responds with an error.

To optimize this scenario, I've set shouldRetryOnError to false since it's impossible for the item to suddenly come into existence. However, even with error retries disabled, SWR attempts to automatically revalidate the data, for example, when switching between tabs. This automatic revalidation triggers another failed call when the item doesn't exist.

Ideally, I would like to revalidate the data only when the item does exist, and skip the revalidation attempts when the item is not found. Is there a recommended approach or workaround within SWR to achieve this behavior?

[alvvaro]

Just remembered I kept this discussion open when I had already found the answer here: #1574 (comment)

It's as simple as:

const swr = useSWR(
    key, fetcher, { shouldRetryOnError: (error) => error.status !== 404 },
);