Error handling in server actions in NextJS - Step-by-Step Execution

Concept Flow - Error handling in server actions

User triggers server action

↓

Server action starts

↓

Try block executes

↓

No error

↓

Return success

↓

Send response

↓

Client receives result

This flow shows how a server action tries to run code, catches errors if any happen, and sends back success or error responses.

Execution Sample

NextJS

export async function action(data) {
  try {
    // process data
    return { success: true };
  } catch (error) {
    return { success: false, message: error.message };
  }
}

A server action tries to process data and returns success or catches errors and returns an error message.

Execution Table

Step	Action	Try Block Result	Catch Block Triggered	Return Value
1	Server action called with data	Not started	No	None
2	Try block runs processing	Success	No	Will return { success: true }
3	Return success response	Success	No	{ success: true }
4	Server action called with bad data	Throws error	Yes	None
5	Catch block runs with error	N/A	Yes	Will return { success: false, message: error.message }
6	Return error response	N/A	Yes	{ success: false, message: error.message }

💡 Execution stops after returning success or error response from server action.

Variable Tracker

Variable	Start	After Step 2	After Step 5	Final
success	undefined	true	false	true or false depending on flow
error	undefined	undefined	Error object	undefined or Error object
message	undefined	undefined	error.message string	undefined or error.message

Key Moments - 3 Insights

Why does the catch block run only sometimes?

The catch block runs only if an error is thrown inside the try block, as shown in execution_table rows 4 and 5.

What happens if no error occurs in the try block?

If no error occurs, the code returns success immediately from the try block, as shown in execution_table rows 2 and 3.

How does the server action communicate errors back to the client?

It returns an object with success: false and an error message from the catch block, as shown in execution_table row 6.

Visual Quiz - 3 Questions

Look at the execution table, what is returned at step 3?

A { success: true }

B { success: false }

C An error object

D No return value

💡 Hint

Check the 'Return Value' column at step 3 in the execution_table.

At which step does the catch block handle an error?

A Step 4

B Step 5

C Step 2

D Step 3

💡 Hint

Look for 'Catch Block Triggered' marked 'Yes' in the execution_table.

If the try block never throws an error, what changes in the variable_tracker?

A success stays false

B error gets assigned an Error object

C success becomes true and error stays undefined

D message gets assigned error.message

💡 Hint

Check variable values after step 2 and step 5 in variable_tracker.

Concept Snapshot

Server actions use try/catch to handle errors.
Try block runs main code.
If error occurs, catch block runs.
Return success or error object accordingly.
Client receives clear success or error response.

Full Transcript

In Next.js server actions, error handling uses a try/catch pattern. When a server action is called, it tries to run the main code inside the try block. If everything works, it returns a success response. If an error happens, the catch block catches it and returns an error response with a message. This way, the client always gets a clear result. The execution table shows each step: starting the action, running try, catching errors if any, and returning results. Variables like success and error change depending on whether an error occurred. This pattern helps keep server actions reliable and easy to debug.

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