Async error handling in routes in Express - Step-by-Step Execution

Concept Flow - Async error handling in routes

Request received

↓

Route handler called

↓

Async operation starts

↓

Async operation resolves or rejects

↓

Send response

↓

Error handling middleware

↓

Send error response

This flow shows how an Express route handles async code: success sends response, errors pass to middleware.

Execution Sample

Express

app.get('/data', async (req, res, next) => {
  try {
    const data = await fetchData();
    res.json(data);
  } catch (err) {
    next(err);
  }
});

An Express route using async/await with try/catch to handle errors and pass them to middleware.

Execution Table

Step	Action	Async Operation Result	Error Caught?	Next Action	Response Sent
1	Request to /data received	N/A	No	Call route handler	No
2	Route handler starts async fetchData()	Pending	No	Wait for result	No
3	fetchData() resolves successfully	Data object	No	Send JSON response	Yes
4	Request to /data received	N/A	No	Call route handler	No
5	Route handler starts async fetchData()	Pending	No	Wait for result	No
6	fetchData() rejects with error	Error object	Yes	Catch block calls next(err)	No
7	Error handling middleware receives error	N/A	Yes	Send error response	Yes

💡 Execution stops after sending response or error response to client.

Variable Tracker

Variable	Start	After Step 3	After Step 6	Final
data	undefined	{...data object}	undefined	{...data object} or undefined
err	undefined	undefined	{Error object}	{Error object} or undefined

Key Moments - 2 Insights

Why do we use try/catch inside async route handlers?

Because async functions can throw errors that must be caught to avoid crashing the server. See execution_table rows 5-6 where error is caught and passed to next().

What happens if we forget to call next(err) in catch block?

The error won't reach the error middleware, so the client may hang or get no response. Execution_table row 6 shows the catch calling next(err) to forward the error.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'data' after step 3?

A undefined

B An error object

C An object with fetched data

D null

💡 Hint

Check variable_tracker row for 'data' after step 3.

At which step does the error get passed to the error handling middleware?

A Step 6

B Step 7

C Step 3

D Step 5

💡 Hint

Look at execution_table rows describing error flow to middleware.

If we remove the try/catch block, what will happen when fetchData() rejects?

A The server will crash or hang without response.

B The response will be sent with empty data.

C The error will be automatically handled by Express.

D The next() function will be called automatically.

💡 Hint

Refer to key_moments about error handling necessity in async routes.

Concept Snapshot

Express async route handlers use try/catch to handle errors.
Inside catch, call next(err) to pass errors to middleware.
Without this, errors can crash server or hang requests.
Async success sends response with data.
Error middleware sends error response to client.

Full Transcript

This visual execution shows how Express handles errors in async route handlers. When a request comes in, the route handler starts an async operation like fetchData(). If it succeeds, the data is sent as JSON response. If it fails, the error is caught in a try/catch block and passed to next(err). This triggers the error handling middleware which sends an error response. Variables like 'data' and 'err' change values during execution. Key moments highlight why try/catch and next(err) are essential to avoid server crashes or hanging requests. The quiz tests understanding of variable states and error flow steps.