Error handling in production in Flask - Step-by-Step Execution

Concept Flow - Error handling in production

Request Received

↓

Process Request

↓

Error Occurs?

No→Send Response

Yes↓

Catch Error

↓

Log Error Details

↓

Return Friendly Error Page

↓

Send Response

This flow shows how Flask handles errors in production by catching exceptions, logging them, and returning a user-friendly error page.

Execution Sample

Flask

from flask import Flask, render_template
app = Flask(__name__)

@app.errorhandler(500)
def internal_error(error):
    app.logger.error(f"Server Error: {error}")
    return render_template('500.html'), 500

This code catches server errors (500), logs them, and returns a custom error page.

Execution Table

Step	Action	Error Occurs?	Logging	Response Sent
1	Request received for /	No	No	Normal page content
2	Request received for /cause-error	Yes (Exception raised)	No	No
3	Error caught by @app.errorhandler(500)	Yes	Yes (Logs error message)	No
4	Return custom 500 error page	No	No	500.html with status 500
5	Response sent to client	No	No	500 error page displayed

💡 Error handled and custom error page sent, stopping further error propagation.

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
error	None	Exception instance	Exception instance	None
response	None	None	None	500.html content

Key Moments - 3 Insights

Why doesn't the server crash when an error occurs in Step 2?

Because the error is caught by the @app.errorhandler(500) function at Step 3, which prevents the crash by handling the exception.

What happens if we don't log the error in Step 3?

Without logging, developers won't see error details in logs, making debugging harder, even though users still get the friendly error page.

Why do we return a custom error page instead of the default error message?

A custom error page improves user experience by showing a friendly message instead of a confusing technical error.

Visual Quiz - 3 Questions

Look at the execution table, what is logged at Step 3?

A The normal page content

B The error message from the exception

C Nothing is logged

D The 500.html page content

💡 Hint

Check the 'Logging' column at Step 3 in the execution_table.

At which step is the custom error page sent to the client?

A Step 2

B Step 4

C Step 5

D Step 3

💡 Hint

Look at the 'Response Sent' column to see when the 500 error page is delivered.

If the error handler was removed, what would happen at Step 3?

A The server would crash or return a default error response

B The custom 500.html page would still show

C The error would be caught and logged anyway

D The request would succeed without error

💡 Hint

Refer to the flow where error catching is essential to prevent crashes.

Concept Snapshot

Flask error handling in production:
- Use @app.errorhandler(code) to catch errors
- Log error details for debugging
- Return friendly error pages (e.g., 500.html)
- Prevent server crashes by catching exceptions
- Improves user experience and maintainability

Full Transcript

In Flask production, when a request causes an error, the app catches it using error handlers like @app.errorhandler(500). This prevents the server from crashing. The error details are logged for developers to review. Then, a friendly error page is sent to the user instead of a raw error message. This flow ensures smooth user experience and easier debugging.

Practice

1. What is the main purpose of using @app.errorhandler in a Flask application?

easy

A. To catch specific errors and provide custom responses

B. To speed up the application startup

C. To automatically restart the server on errors

D. To log user activities

Solution

1. Step 1: Understand the role of @app.errorhandler

   This decorator is used to catch specific HTTP or application errors in Flask.

2. Step 2: Recognize its use for custom responses

   It allows developers to return user-friendly error pages or messages instead of default error traces.

3. Final Answer:

   To catch specific errors and provide custom responses -> Option A

4. Quick Check:

   Error handling = custom responses [OK]

Hint: Errorhandler decorates functions to catch and respond to errors [OK]

Common Mistakes:

• Thinking it restarts the server automatically
• Confusing errorhandler with logging functions
• Assuming it speeds up app startup

2. Which of the following is the correct syntax to handle 404 errors in Flask?

easy

A. @app.error(404)
def not_found(error):
return 'Not found', 404

B. @app.errorhandler(404)
def not_found(error):
return 'Page not found', 404

C. @app.handle_error(404)
def not_found():
return 'Page missing', 404

D. @app.catch_error(404)
def not_found(error):
return '404 error', 404

Solution

1. Step 1: Identify the correct decorator name

   The correct Flask decorator for error handling is @app.errorhandler.

2. Step 2: Confirm function signature and return

   The function should accept an error parameter and return a response with the error code.

3. Final Answer:

   @app.errorhandler(404)\ndef not_found(error):\n return 'Page not found', 404 -> Option B

4. Quick Check:

   Correct decorator and function signature = @app.errorhandler(404) def not_found(error): return 'Page not found', 404 [OK]

Hint: Use @app.errorhandler with error code and error param [OK]

Common Mistakes:

• Using wrong decorator names like @app.handle_error
• Omitting the error parameter in the function
• Returning without the status code

3. Given this Flask code snippet, what will the user see if a 500 error occurs?

@app.errorhandler(500)
def internal_error(error):
    return 'Something went wrong, please try later.', 500

medium

A. The message: 'Something went wrong, please try later.' with status 500

B. A detailed Python traceback error page

C. A blank page with status code 500

D. The default Flask 404 error page

Solution

1. Step 1: Understand the errorhandler function

   The function returns a custom message and status code 500 when a 500 error occurs.

2. Step 2: Identify the user-visible output

   The user will see the returned string message with HTTP status 500, not the default traceback.

3. Final Answer:

   The message: 'Something went wrong, please try later.' with status 500 -> Option A

4. Quick Check:

   Custom error message shown = The message: 'Something went wrong, please try later.' with status 500 [OK]

Hint: Custom errorhandler returns your message, not default trace [OK]

Common Mistakes:

• Expecting Flask's default error page instead of custom message
• Thinking a blank page will appear
• Confusing 500 error with 404 error page

4. What is wrong with this Flask error handler code?

@app.errorhandler(403)
def forbidden():
    return 'Access denied', 403

medium

A. The return statement must include a JSON response

B. The decorator should be @app.handle_error

C. The function must accept an error parameter

D. The status code 403 is invalid

Solution

1. Step 1: Check function signature for errorhandler

   Flask error handler functions must accept the error argument to receive error details.

2. Step 2: Identify missing error parameter

   The function forbidden lacks the required error parameter.

3. Final Answer:

   The function must accept an error parameter -> Option C

4. Quick Check:

   Error handler function needs error param = The function must accept an error parameter [OK]

Hint: Error handler functions always take an error argument [OK]

Common Mistakes:

• Omitting the error parameter in handler functions
• Using wrong decorator names
• Assuming JSON response is mandatory

5. You want to show a friendly error page for all unhandled exceptions in production without exposing debug info. Which Flask setup is best?

hard

A. Use @app.route('/error') to manually show errors

B. Set app.debug = True to see detailed errors

C. Remove all error handlers to let Flask show default error pages

D. Use @app.errorhandler(Exception) to catch all errors and return a simple message

Solution

1. Step 1: Understand catching all exceptions

   Using @app.errorhandler(Exception) catches all unhandled errors globally.

2. Step 2: Provide user-friendly message without debug info

   Returning a simple message hides technical details, improving user experience and security.

3. Final Answer:

   Use @app.errorhandler(Exception) to catch all errors and return a simple message -> Option D

4. Quick Check:

   Global error handler with simple message = Use @app.errorhandler(Exception) to catch all errors and return a simple message [OK]

Hint: Catch Exception globally to hide debug info in production [OK]

Common Mistakes:

• Enabling debug mode in production
• Relying on default Flask error pages
• Using routes instead of error handlers for errors