Error handling in server actions in NextJS

Introduction

Error handling in server actions helps you catch problems and respond properly, so your app stays reliable and users get clear feedback.

When saving user data to a database and you want to handle failures gracefully.

When calling external APIs from a server action and need to manage errors like timeouts.

When validating input on the server and returning error messages for invalid data.

When performing file uploads or downloads and you want to catch issues like missing files.

When you want to log errors on the server for debugging and monitoring.

Syntax

NextJS

export async function actionName(formData) {
  try {
    // your server logic here
    return { success: true };
  } catch (error) {
    // handle error
    return { error: error.message };
  }
}

Use try...catch to catch errors inside server actions.

Return error info in a structured way so the client can show messages.

Examples

Catches database save errors and returns a simple error message.

NextJS

export async function saveUser(data) {
  try {
    await database.save(data);
    return { success: true };
  } catch (error) {
    return { error: 'Failed to save user.' };
  }
}

Handles network or API errors and returns the error message.

NextJS

export async function fetchData() {
  try {
    const response = await fetch('https://api.example.com/data');
    if (!response.ok) throw new Error('API error');
    const data = await response.json();
    return { data };
  } catch (error) {
    return { error: error.message };
  }
}

Sample Program

This server action checks login data, throws errors for missing or wrong info, and returns success or error messages. It also sets a cookie on success.

NextJS

import { cookies } from 'next/headers';

export async function loginAction(formData) {
  try {
    const username = formData.get('username');
    const password = formData.get('password');

    if (!username || !password) {
      throw new Error('Username and password are required');
    }

    // Simulate user check
    if (username !== 'admin' || password !== '1234') {
      throw new Error('Invalid credentials');
    }

    // Set a cookie on successful login
    cookies().set('token', 'fake-jwt-token');

    return { success: true };
  } catch (error) {
    return { error: error.message };
  }
}

Important Notes

Always return errors in a consistent format so the client can handle them easily.

Do not expose sensitive error details to users; keep messages friendly and safe.

Use try...catch blocks inside server actions to catch both synchronous and asynchronous errors.

Summary

Error handling keeps your app stable and user-friendly.

Use try...catch inside server actions to catch and return errors.

Return clear error messages so the client can show helpful feedback.

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