Wrapping Next.js redirect() in try/catch blocks silently breaks navigation

In Next.js, the redirect() function works by throwing a special internal error that the framework catches at a higher level to trigger navigation. Placing redirect() inside a try/catch block causes that internal signal to be intercepted and suppressed, so the redirect never actually occurs. Instead, the catch block logs a misleading 'Login failed' error and returns a generic failure response, even when the login was fully successful. The fix is to scope the try/catch only around genuinely risky operations, such as database calls, and call redirect() outside the block entirely. If a broader try/catch is unavoidable, developers should explicitly re-throw any Next.js internal redirect or notFound signals rather than swallowing them.