Do you have any Next.js config options enabled?

Also, maybe this is what Next.js is going for in version 15, now that certain APIs (including search params) mark components as dynamic and you need to wrap them in <Suspense>.
Looking at the error log, it seems like you’re trying to pre-render (statically generate) a page and inside that page your client component needs to access SearchParams, and accordingly to the docs that should need a Suspende boundary:

If a route is statically rendered, calling useSearchParams will cause the Client Component tree up to the closest Suspense boundary to be client-side rendered.

I currently only have this configured in the next.js config

import type { NextConfig } from "next";

const nextConfig: NextConfig = {
  experimental: {
    serverActions: {
      bodySizeLimit: "30mb",
    },
  },
  images: {
    contentDispositionType: "inline",
    remotePatterns: [
        ...
    ],
  },
};
export default nextConfig;

And yeah, I read that part of the documentation but it confuses me because underneath it mentions that it “recommends” wrapping, but it does not say that it is mandatory.

And yeah, I get the error on a page /panel/users which is rendered statically and is asynchronous, because I use a component in the page that uses the hook useSearchParams and is marked as 'use client'.

But. I managed to make the build of my project without errors, but I don't really understand now what is the problem actually hahaha, I wrapped with Suspense one of the most recent components that I have made in the project, this component is not used directly in a page.tsx or in a layout.tsx, but it is used inside another parent component, which is marked with use client also, and already this parent component is the one used in a layout.tsx.

And this made me not to get the Suspense error in the build, but I only had to modify this component, and nothing else, so I'm really confused haha.

Just a side node, when your components suspend, meaning they’re accessing async data, what happens under the hood is that React throws a special error as soon as it encounters an async operation (a promise). <Suspense> boundary catches that error and handles it while the async operation is running on the back, and allows you to provide a fallback UI for a nice UX. React keeps track of the suspended component and when the promise inside has been resolved, React re-renders the component with the latest data, and now the component is shown instead of the fallback UI.
So, by not wrapping in <Suspense> that little nested component that seemed innocent, now you’re letting the special error bubble up the whole route, affecting the expected result.

Short answer: yes. It is a requirement from v15.

Ok, so it could be said that in a way it’s required to wrap any component that uses useSearchParams() in Suspense in Next.js version 15, although I still don’t get why in some cases it causes conflicts and in others it doesn’t haha (when building the project). Thanks a lot to both of you

I finally got why I don’t have issues using the other components that use the hook on the other pages.tsx. it’s because those are rendered dynamically, they show up like that after the build is done, I mark them as async and I fetch data in those pages, which is why they don’t cause conflicts. Sorry about that, I didn’t fully understand this earlier haha.

Exactly, glad it clicked for you now! Make sure to mark the solution 👍

kk thanks