> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/blynk.console/devices/device-profile/developer-tools/actions-log.md).

# Actions Log

This table contains every datastream action sent through Blynk.Cloud for this device.

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

This section is crucial for tracking activities, diagnosing issues, and auditing changes. The Actions Log tab provides a comprehensive history of actions performed on the datastream.

Table view can be **sorted** by each of 5 data types represented by columns (mind the lazy loading please):

### Filter Options

#### **Time Filter**

Applies to time when device's datastream change was made. Allows you to filter the actions log based on predefined time ranges. Options include:

* 1 hour (1h)
* 6 hours (6h)
* 1 day (1d)
* 1 week (1w)
* 1 month (1mo)
* 3 months (3mo)
* Custom filter icon for more specific date range selections.

#### **Name**

The name of the user or system entity that performed the action.

#### **Client**

The type of client or interface used to perform the action. Multiple clients can be selected. Example Values:

* Alexa
* Android
* Automation
* Google Home
* HTTPS API
* iOS
* Terminal
* Web
* Other


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.blynk.io/en/blynk.console/devices/device-profile/developer-tools/actions-log.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.