"use client"; /* The route-level error boundary. Something threw while rendering a page; the shell survives, so this keeps the site's own chrome and offers the two things that actually help — try again, and a way to tell someone. The error's message is deliberately not printed: it is written by the server, can carry internal detail, and means nothing to a linen services manager. The digest is shown because it is the one string that lets a report be matched to a log line. */ import Link from "next/link"; import { useEffect } from "react"; import { reportError } from "@/lib/errors"; export default function Error({ error, reset }: { error: Error & { digest?: string }; reset: () => void }) { useEffect(() => { reportError(error, "route"); }, [error]); return (
Something went wrong

This page didn’t load.

The fault is ours, not yours, and nothing you were doing has been lost — ThreadCount only changes a record when you commit it. Try again, and if it keeps happening, tell us and we’ll go and look.

Back to the start Tell us
{error.digest ? (

Reference {error.digest} — quote this and we can find it in the log.

) : null}
); }