# Activity and Order History

Cortex provides full execution visibility for every server-side task, including fill history, errors, and lifecycle tracking.

### Activity Panel

All Cortex tasks appear in the Activity panel alongside your client side activity. Each task displays:

* **Symbol:** the instrument being traded
* **Type:** the order or algorithm type (e.g. TWAP, Chase)
* **Progress:** completion percentage
* **Duration:** elapsed time since the task started
* **Size:** total order size
* **Price:** current or average fill price
* **Details:** configuration summary (jitter, method, etc.)

You can expand any task to see detailed execution information and cancel running tasks at any time.

<figure><img src="/files/jixoG6G1k8VyEme2QaOc" alt=""><figcaption></figcaption></figure>

### Execution History

Every Cortex task maintains a full execution history. For each lot or fill within a task, you can see:

* Fill status (filled, pending, failed)
* Execution price
* Filled size vs. target size
* Timestamp of execution

### Error Visibility

If an error occurs during execution -- for example, an exchange rejection or insufficient margin -- the error is surfaced with details in the task's execution history. This makes it straightforward to diagnose issues with long-running orders.

### Cross-Device Access

Activity and order history are available from any device logged into your account. There is no need to be on the same device that created the order.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.insilicoterminal.com/documentation/cortex/activity-and-order-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.