Catch up on highlights from Firebase at Google I/O 2023. Learn more

Report errors

Automatically reporting errors

You can emit an error from a Cloud Function to Error Reporting as shown below:


// These WILL be reported to Error Reporting
throw new Error('I failed you'); // Will cause a cold start if not caught


def hello_error_1(request):
    # This WILL be reported to Error Reporting,
    # and WILL NOT show up in logs or
    # terminate the function.
    from import error_reporting
    client = error_reporting.Client()

        raise RuntimeError('I failed you')
    except RuntimeError:

    # This WILL be reported to Error Reporting,
    # and WILL terminate the function
    raise RuntimeError('I failed you')
def hello_error_2(request):
    # These errors WILL NOT be reported to Error
    # Reporting, but will show up in logs.
    import logging
    import sys
    print(RuntimeError('I failed you (print to stdout)'))
    logging.warning(RuntimeError('I failed you (logging.warning)'))
    logging.error(RuntimeError('I failed you (logging.error)'))
    sys.stderr.write('I failed you (sys.stderr.write)\n')

    # This is considered a successful execution and WILL NOT be reported
    # to Error Reporting, but the status code (500) WILL be logged.
    from flask import abort
    return abort(500)

If you would like more fine-grained error reporting, you can use the Error Reporting client libraries.

You can view the reported errors in Error Reporting in the GCP Console. You can also see the errors reported from a particular function when you select it from the list of functions in the GCP Console.

Uncaught exceptions produced by your function will appear in Error Reporting. Note that some types of uncaught exceptions (such as those thrown asynchronously) will cause a cold start to occur upon a future function invocation. This increases the amount of time your function will take to run.

Manually reporting errors

Sending to Cloud Logging

The error function from the Cloud Functions logger SDK will report errors to both Cloud Logging and Error Reporting. To include more context from the error as structured data, pass an error object as the second argument:

} catch (err) {
  // Attach an error object as the second argument
    "Unable to read quote from Firestore, sending default instead",