---
title: .NET agent reports handled errors
source: https://docs.newrelic.com/docs/apm/agents/net-agent/troubleshooting/net-agent-reports-handled-errors
---

## Problem

New Relic's .NET agent reports handled errors as though they are standard errors. This is most common with Azure worker roles, console apps, async work, and similar operations.

## Solution

To avoid false error reports, instrument a method that directly or indirectly contains the exception handler. Instrument the target method by defining a [custom instrumentation](https://docs.newrelic.com/docs/agents/net-agent/custom-instrumentation/introduction-net-custom-instrumentation) file, or by wrapping the method in a [custom transaction](https://docs.newrelic.com/docs/agents/net-agent/custom-instrumentation/create-transactions-xml-net), as shown in this example:

**GetResponse() throws an error**

In this example, New Relic reports an error from `GetResponse()` **unless** the method `Foo()` is instrumented. As long is `Foo` is instrumented, New Relic begins a transaction when `Foo` is called and ends the transaction when `Foo` ends.

Because the error is handled before `Foo` ends, New Relic will not report an error. Note also that `GetResponse()` becomes a segment of the `Foo` transaction.

````cs
using System;
using System.Collections.Generic;
using System.Threading;
using System.Threading.Tasks;
using System.Net;
using System.IO;

namespace ErrorTester
{
    class Program
    {
        static void Main(string[] args)
        {
            var i = 0;
            while (true)
            {
                Foo(++i);
            }
        }

        static void Foo(int i)
        {
            try
            {
                GetNotFound();
            }
            catch (Exception ex)
            {
                Console.WriteLine("Got it " + i + "!");
                Thread.Sleep(1000);
            }
        }

        static string GetNotFound()
        {
            string uri = "https://localhost/Test/this/is/not/a/real/page";
            var request = (HttpWebRequest)WebRequest.Create(uri);
            var response = request.GetResponse();
            var data = new StreamReader(response.GetResponseStream()).ReadToEnd();
            response.Close();
            return data;
        }
    }
}
```

````

**Define a custom instrumentation file**

To instrument `Foo`:

1.  Define a [custom instrumentation file](https://docs.newrelic.com/docs/agents/net-agent/custom-instrumentation/introduction-net-custom-instrumentation); for example, `CustomInstrumentation.xml`:

    ```xml
    <?xml version="1.0" encoding="utf-8"?>
    <!-- © 2008-2014 New Relic, Inc. All rights reserved. -->
    <!--
        When you edit this file, please use an XML aware editor (such as Visual Studio),
        and pair with the companion file extension.xsd to minimize the
        chance of introducing typos that may confuse the agent when it is run.
    -->
    <extension xmlns="urn:newrelic-extension">
      <instrumentation>
        <tracerFactory >
          <match assemblyName="ErrorTester" className="ErrorTester.Program">
            <exactMethodMatcher methodName="Foo" /> 
          </match>
        </tracerFactory>
      </instrumentation>
    </extension>
    ```
2.  Place `CustomInstrumenation.xml` in the New Relic extensions folder, alongside `CoreInstrumentation.xml`, and restart your application.

**Wrap the method in a custom transaction**

To instrument `Foo`, wrap it in a [custom transaction](https://docs.newrelic.com/docs/agents/net-agent/custom-instrumentation/create-transactions-xml-net):

````xml
<extension xmlns="urn:newrelic-extension">
  <instrumentation>
     <tracerFactory name="NewRelic.Agent.Core.Tracer.Factories.BackgroundThreadTracerFactory" metricName="Background/Task">
       <match assemblyName="ErrorTester" className="ErrorTester.Program">
         <exactMethodMatcher methodName="Foo" />
       </match>
    </tracerFactory>
  </instrumentation>
</extension>
```

````

## Cause

The only errors New Relic's .NET agent reports are unhandled errors that end a transaction. If your app calls an exception handler before the transaction ends, New Relic will not report an error.

However, New Relic does not always detect exception handlers when the error occurs outside of a web transaction, WCF transaction, or custom transaction. This is because the agent creates "mini-transactions" for instrumented methods that are not associated with a transaction.

When the instrumented method exits, the mini-transaction ends. If the mini-transaction throws an error and the instrumented method does not handle it, then New Relic will report an error.

You can see this in a console app that calls `GetResponse()`, as shown in the [example](#get-response-block). If `GetResponse` throws an error, then New Relic will report it, even though `GetResponse()` is called within a try/catch block. The agent reports an error because the `GetResponse()` "mini-transaction" ended and the error was still unhandled on transaction exit.