next.js: ISR fails to serve 404 pages once the page gets deleted if experimental isr memory cache size is set to 0

Same issue on 13.0.3

This makes self hosting isr almost impossible in those cases when we want to remove pages and have shared static cache between instances.

Still present on 13.1.6.

• Page generated on build
• DB updated to disable the page
• Revalidation api called
• Stale page still served (despite notFound: true being returned)
• Works if removing isrMemoryCacheSize: 0 from next.config.js (but we need this due to shared mount resources)

I have done a workaround for this issue that might save someone else suffering from this issue: https://stackoverflow.com/questions/75731978/how-can-you-delete-statically-generated-nextjs-files-on-404-and-redirects

TLDR; - this is an implementation of how to delete the statically generated files yourself. The concept is for a single non-shared mount, so more exotic hosting setups might not be helped by this, but maybe.

I’ve made a workaround by passing a specific prop in the getStaticProps, and implementing a client-side redirect to the 404 page:

const Page = ({props}) => {
  const router = useRouter();
  useEffect(() => {
    if (props.notFound) {
      router.push('/404');
    }
  }, [notFound, router]);

  if (notFound) {
    return null;
  }
  renderPage(props)
}
export const getStaticPaths: GetStaticPaths = async () => {
  const document = await getDocument()
  if (document) {
    return {props: {...document } }; 
  }
  return {props: {notFound: true}}
}

I know that solution is not ideal, because the page is still in the memory, but redirect is working and as we don’t pass other props, the size of next-data will be reduced.

Same issue here. Will this get fixed?