---
title: "How To Find an Error's Exception Code"
canonical: "https://resourcecenter.kenect.com/space/Messaging/41943699/How%20To%20Find%20an%20Error's%20Exception%20Code"
format: markdown
---
### Web services record all of the information they send and receive. This data is typically stored in your browser's developer console. When Kenect is presenting an error or has a non-working button, there are additional details hiding in the **Network activity**. Combined with internal logs, Support can use this information to quickly diagnose those issues.

> ℹ️ NOTE: If you are *not getting an error* in the network console, it is still possible to locate a traceable ID that can help us learn about the problem in our internal logs. Step 6 will cover this in detail (video example included).

### **Here's how to find the information we need:**

1. To find an error's exception code, you *need to be able to reproduce the issue*. Assuming you can do so, navigate back to the exact button/menu/prompt/kabob that you click to produce the error, but **don't click it yet**!
2. Open the Google Chrome **Network** activity monitor. This can be done a few different ways:
  - Pressing ***Ctrl+Shift+I*** on Windows or ***Cmd+Option+I*** on Mac.
  - Right click anywhere on the page and select ***Inspect***.
  - Open the **Chrome kebab menu** > **More tools** > **Developer tools**.
3. Once it's open, verify that you're on the Network tab, and that recording has started (the red dot). Then, click the Clear button (🛇) to clean out existing data:
4. Now you can recreate the error/issue. Press the button, open the menu, try saving the changes, etc. You will see the Network logs fill up with information. We're looking for any of these items that are colored Red. Click that item to open it, and navigate to the Preview or Response tab in search of an exceptionTypeCode:
    
5. Copy that code and add it to your ticket. The Support Team have access to internal logs they can search using this code for more information about the error or what caused it. Please note that there may be more than one **Red** event, and therefore more than one exception code: be sure to include them all.
  Notice how the error message in Kenect reads "***You do not have permissions to...***"? As I'm sure you know, there are lots of errors which DO NOT produce that handy error message. The good news is, these messages are still hiding somewhere in the system and just haven't been added to the application yet. If you locate the exception code, Support can find you that information and vastly improve the turnaround time on resolving your Bug Reports.
6. (Optional): If you are not getting an error or do not see red text, there is still valuable information here that can help us search the logs. The red 'refer-to-locations' example above is an API Endpoint. Even when the calls to these endpoints are successful (i.e. they're NOT red), they still have a traceable ID attached. In Kenect, ours is called "x-cloud-trace-context". In this example, I've just connected a Facebook page to my test Org/Location. By searching 'Facebook' in the console search bar, I can see all events/endpoints which have Facebook in the name. If I know which endpoint I'd like to check in the logs, I can click it and find the x-cloud-trace-context on the Headers tab:
    PLEASE NOTE: as of writing this (November 2022), not all activities in Kenect have been enabled to provide this code. Therefore, an error with an exception code is still the more reliable method for investigating an issue.The problem here is that you may not know which endpoint to get the trace for. There is no simple way to learn this without being intimately familiar with Kenect's code. For now, when the need arises to retrieve the x-cloud-trace-context ID, either:
    Grab the value for each network event that looks/sounds important.  
Reach out to Support and ask them which value might be helpful for your specific issue.

### Thank you for everything you do in improving the Bug Report process. Together, we can help our customers focus less on the issues and more on the success of their business.

 

Please let us know if you have any questions regarding this process/the article.