Manually preventing a page revalidation

[pepew-le-boss]

Is there a way to manually prevent a page revalidation ?
Let's take this scenario:

page:

export const revalidate = 600 // 10 minutes

export default async function HomePage() {
  return (
    <>
      <Suspense fallback={<Skeleton className="h-full w-full" />}>
        <CategoriesWrapper />
      </Suspense>
      <div>more static content ...</div>
    </>
  )
}

CategoriesWrapper:

export async function CategoriesWrapper() {
  const categoriesResponse = await graphqlServerRequest({
    document: categoriesQuery,
    onError() {
      // here I would like to prevent the revalidation of the page
      return undefined
    },
  })

  const categories = categoriesResponse?.categories

  if (!categories) {
    return null
  }

  return <Categories categories={categories} />
}

Currently, if a user visits the website after 10 minutes and revalidates the page, an error in the categoriesQuery will result in the page being cached with empty categories for the next 10 minutes.

I've tried with revalidatePath("/") but I get this error:
Page changed from static to dynamic at runtime /, reason: revalidatePath / see more here https://nextjs.org/docs/messages/app-static-to-dynamic-error

[icyJoseph]

Maybe you could throw an exception? https://nextjs.org/docs/app/building-your-application/data-fetching/incremental-static-regeneration#handling-uncaught-exceptions

If an error is thrown while attempting to revalidate data, the last successfully generated data will continue to be served from the cache. On the next subsequent request, Next.js will retry revalidating the data.