
## Find a request {#find}

Open [Tunnels → Requests](https://dashboard.adal.cloud/tunnels/requests). Filter by **Region**, **Tunnel** or **Status** and use **Order** to put the newest or oldest requests first. Open a row to see its HTTP code, timestamps and the Endpoint used for that request, when available. The list can include requests from deleted tunnels.

## Read the outcome {#statuses}

| Status | Meaning |
|---|---|
| **In progress** | The exchange is still open and has no recorded HTTP or transfer failure. |
| **Success** | The transfer completed without a recorded error and the HTTP code is below 400. A returned redirect can therefore be a success in the journal. |
| **Failed** | The HTTP code is 400 or higher, a transfer error was recorded, or a finished exchange did not complete its transfer. |

**Endpoint** means the local application generated the HTTP response. **Platform** means Adal generated it. If no response was received, the list can show **No HTTP response**. Check **Transfer complete** or **Transfer incomplete** separately from the HTTP code. For example, an Endpoint can send HTTP 200 and then disconnect before the body is fully transferred.

## Timestamps and connection state {#timing}

**Received**, **Delivered** and **Delete after** are shown in UTC. **Delivered** is shown after a complete transfer with a response from the Endpoint. **Delete after** is the expiration time for stored HTTP details and bodies.

The tunnel's **Online**, **Offline** or **Disabled** label describes its current connection state. It can change independently of past requests. Likewise, the HTTP outcome is independent of whether request and response data were saved.

## Investigate a failure {#troubleshooting}

1. Check the HTTP code, response source and transfer completion.
2. For an **Endpoint** response, check your application's logs and reproduce the call directly from the machine running CLI.
3. For a **Platform** response or incomplete transfer, check the [tunnel error and connection guide](/en/docs/tunnels/adal-cli#troubleshooting). Use [HTTP data and downloads](/en/docs/tunnels/http-data) to see which parts were saved.

The journal preserves past outcomes. To test a fix, send a new request from a client you control.
