Error handling in server actions in NextJS - Performance & Optimization

Performance: Error handling in server actions

MEDIUM IMPACT

This affects the responsiveness and stability of server actions, impacting how quickly errors are detected and handled without blocking the UI.

Handling errors in server actions to avoid blocking UI updates

NextJS

export async function action(data) {
  try {
    const result = await fetch('/api/process', { method: 'POST', body: JSON.stringify(data) });
    if (!result.ok) throw new Error('Failed request');
    return await result.json();
  } catch (error) {
    return { error: error.message };
  }
}

Catching errors and returning a controlled error object allows the UI to update immediately with feedback, avoiding blocking.

📈 Performance GainNon-blocking UI update, reduces INP by 100-300ms compared to unhandled errors

Handling errors in server actions to avoid blocking UI updates

NextJS

export async function action(data) {
  try {
    const result = await fetch('/api/process', { method: 'POST', body: JSON.stringify(data) });
    if (!result.ok) throw new Error('Failed request');
    return await result.json();
  } catch (error) {
    throw error; // rethrow without handling
  }
}

Rethrowing errors without handling causes unhandled promise rejections, blocking UI updates and causing poor user experience.

📉 Performance CostBlocks rendering until error bubbles up, increasing INP by 100-300ms depending on network

Performance Comparison

Pattern	Server Blocking	UI Blocking	Error Feedback Speed	Verdict
Rethrow errors without handling	No blocking on server but unhandled promise rejection	Blocks UI update until error bubbles	Slow feedback, delayed error display	[X] Bad
Catch errors and return error object	No blocking	Immediate UI update with error	Fast feedback, smooth user experience	[OK] Good
Synchronous infinite loop on error	Blocks server event loop	Blocks all UI updates	No feedback, server freeze	[X] Bad
Log error and return controlled message	No blocking	Immediate UI update	Fast feedback, stable server	[OK] Good

Rendering Pipeline

Error handling in server actions affects the server response phase and the client update phase. Proper handling ensures the server sends a timely response and the client can render error states without delay.

→Server Processing

→Network Response

→Client Rendering

⚠️ BottleneckServer Processing when errors are unhandled or blocking

Core Web Vital Affected

INP

This affects the responsiveness and stability of server actions, impacting how quickly errors are detected and handled without blocking the UI.

Optimization Tips

1Always catch errors in server actions to prevent unhandled promise rejections.

2Avoid synchronous blocking code in error handlers to keep the server responsive.

3Return structured error responses to enable fast client UI updates.

Performance Quiz - 3 Questions

What is the main performance risk of rethrowing errors without handling in Next.js server actions?

A It blocks UI updates causing slow interaction response

B It increases bundle size significantly

C It causes layout shifts on the page

D It improves server response time

DevTools: Performance

How to check: Record a performance profile while triggering server actions with errors. Look for long tasks or blocked frames during error handling.

What to look for: Check for long blocking tasks on the main thread or server response delays indicating poor error handling.

Practice

1. What is the main purpose of using try...catch blocks inside Next.js server actions?

easy

A. To manage state in React components

B. To improve client-side rendering speed

C. To catch errors and handle them gracefully during server-side operations

D. To style components dynamically

Solution

1. Step 1: Understand server actions role

   Server actions run on the server and can fail due to errors like invalid input or database issues.

2. Step 2: Purpose of try...catch

   Using try...catch allows catching these errors and responding properly instead of crashing the app.

3. Final Answer:

   To catch errors and handle them gracefully during server-side operations -> Option C

4. Quick Check:

   Error handling = To catch errors and handle them gracefully during server-side operations [OK]

Hint: Try...catch in server actions catches server errors [OK]

Common Mistakes:

• Confusing client-side state management with server error handling
• Thinking try...catch improves UI styling
• Assuming try...catch speeds up rendering

2. Which of the following is the correct syntax to throw an error inside a Next.js server action?

easy

A. throw new Error('Invalid input')

B. raise Error('Invalid input')

C. error('Invalid input')

D. throw Error: 'Invalid input'

Solution

1. Step 1: Recall JavaScript error throwing syntax

   JavaScript uses throw new Error('message') to create and throw errors.

2. Step 2: Check options for correct syntax

   Only throw new Error('Invalid input') matches the correct syntax; others use invalid keywords or formats.

3. Final Answer:

   throw new Error('Invalid input') -> Option A

4. Quick Check:

   Throw error syntax = throw new Error('Invalid input') [OK]

Hint: Use 'throw new Error(message)' to throw errors [OK]

Common Mistakes:

• Using 'raise' instead of 'throw'
• Missing 'new' keyword before Error
• Incorrect punctuation in throw statement

3. Consider this Next.js server action code:

export async function addUser(data) {
  try {
    if (!data.name) throw new Error('Name is required');
    // pretend to save user
    return { success: true };
  } catch (error) {
    return { success: false, message: error.message };
  }
}

What will addUser({}) return?

medium

A. { success: false, message: 'Name is required' }

B. { success: true }

C. Throws an uncaught error

D. Returns undefined

Solution

1. Step 1: Analyze input and error condition

   The input object is empty, so data.name is falsy, triggering the error throw.

2. Step 2: Understand catch block behavior

   The thrown error is caught, and the function returns an object with success: false and the error message.

3. Final Answer:

   { success: false, message: 'Name is required' } -> Option A

4. Quick Check:

   Error caught returns failure object = { success: false, message: 'Name is required' } [OK]

Hint: Empty name triggers error, caught returns failure object [OK]

Common Mistakes:

• Assuming error is uncaught and crashes
• Expecting success true despite missing name
• Thinking function returns undefined

4. Identify the error in this Next.js server action code:

export async function updateUser(data) {
  try {
    if (!data.id) throw Error('User ID missing');
    // update logic
  } catch {
    return { error: 'Update failed' };
  }
}

medium

A. Try block should not throw errors

B. Missing parentheses in throw statement

C. Function must return a value on success

D. Catch block missing error parameter

Solution

1. Step 1: Check throw statement syntax

   The throw statement is valid without 'new', so no syntax error there.

2. Step 2: Inspect catch block syntax

   The catch block lacks an error parameter, which is allowed in modern JS but prevents accessing error details inside catch.

3. Step 3: Evaluate best practice

   Without error parameter, you cannot log or use the error object, which is a common mistake in error handling.

4. Final Answer:

   Catch block missing error parameter -> Option D

5. Quick Check:

   Catch needs error param to handle error details [OK]

Hint: Always include error parameter in catch for details [OK]

Common Mistakes:

• Assuming throw without new is invalid
• Ignoring missing return on success
• Thinking try should never throw

5. You want to create a Next.js server action that validates user input and throws an error if the email is invalid. Which approach correctly combines validation and error handling?

hard

A. Throw error outside try block and catch inside to handle validation

B. Use try...catch to validate email format and throw new Error if invalid, then catch and return error message

C. Validate email on client only; server action should not throw errors

D. Return error messages without throwing errors in server actions

Solution

1. Step 1: Understand server action validation

   Server actions should validate inputs and throw errors if invalid to prevent bad data.

2. Step 2: Proper error handling pattern

   Use try...catch to throw new Error on invalid email and catch it to return a clear message.

3. Step 3: Evaluate options

   Use try...catch to validate email format and throw new Error if invalid, then catch and return error message correctly uses try...catch with throwing errors; others either skip server validation or misuse error handling.

4. Final Answer:

   Use try...catch to validate email format and throw new Error if invalid, then catch and return error message -> Option B

5. Quick Check:

   Validate + throw + catch = Use try...catch to validate email format and throw new Error if invalid, then catch and return error message [OK]

Hint: Validate input inside try, throw error, catch and return message [OK]

Common Mistakes:

• Skipping server-side validation
• Throwing errors outside try block
• Returning errors without throwing