Pauline P. Narvas Hey, @lennsend170683-4600! Welcome 👋 Quick debugging steps: Open browser DevTools Console and check for errors when switching tabs Look for event listeners on window.blur, document.visibilitychange, or similar Try disabling browser extensions that might interfere Check if the issue happens in all browsers or just one For a proper fix, you’ll likely need to update how your CRM handles state persistence. Let us know!
Lennsend170683 4600 Hi Pauline, I honestly have no idea what Im looking at sorry. Is this any help? Regards Lenn
Lennsend170683 4600 @pawlean not sure if that was any help at all?
Pauline P. Narvas Is your application client-side rendered static site? Static site requests don’t appear in runtime, only function invocations do. This is expected behavior for React apps without server-side functionality.
ADALIGO If your React app is purely client-side rendered (CSR) or a static site, this is expected. Vercel runtime logs only capture server-side invocations, like API routes or serverless functions. Static pages served by React won’t appear in runtime logs, even if traffic is coming in. A couple of things you could check: Are you using Next.js with any server-side functions or API routes? Those logs will show. If not, you’d need to route logging through a serverless function to capture requests in Vercel logs.