> For the complete documentation index, see [llms.txt](https://docs.gradient.works/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gradient.works/kb/routing/automation/log-entries.md).

# Log Entries

Log Entries are great for finding out what happened with a particular assignment. If you ever need to track down an issue, Log Entries are an important part of debugging.

### Creating Log Entries

The built-in ABK actions generate log entries as they execute. You can generate your own custom log entries in your automations by using the [Log Message](/kb/automation-builder-kit-abk/actions/logging/logaction.md) ABK action in your Flows.

### Locating Log Entries

Log entries are available in two places:

1. The Log Entries tab (see below)
2. In [Automation Executions](/kb/routing/automation/automation-executions.md) for those automations built with [Flow Lifecycle](/kb/automation-builder-kit-abk/actions/leads.md) actions

### Log Entries Tab

All log entries are located in the Log Entries tab via a standard Salesforce list. You can create and save filter views for this list just like any other standard list.

1. On the Gradient Works Tab, click Log Entries

![](/files/LpQoFnczliLSLZfS5mXq)

2. Make sure the List View is toggled to "All"
3. The next thing you'll want to do is filter the view to the specific assignment you're looking for.

* On the top right screen click on the Funnel icon and you can start filtering the view to meet your specific assignment

![](/files/3uStG7nv6DO1yOVGrmkF)

* The more information you know about the assignment you're hoping to track the better. Our recommendation is to start filtering from the time the assignment happened, this will allow you to view all the logs that happened during that time.

![](/files/mJ71xkKfL33Z07Xc9WAM)

* The corresponding results of the newly filter log page should look something like this:

![](/files/8ALoTDBtb0yOiB11d9Mf)

* From here, you'll be able to click on the log entry that should give you more information on why an assignment happened or why a particular error happened on that assignment.

4. If more support is needed please contact <support@gradient.works> with any information you're able to provide from the Log Entries.


---

# 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.gradient.works/kb/routing/automation/log-entries.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.