> For the complete documentation index, see [llms.txt](https://docs.dckapintegrator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dckapintegrator.com/project-manager/workflows/actions/detail-logger.md).
# Detail Logger
Detail Logger is similar to the Error Logger but is used to provide logs at the item level. Detail Logger marks every single entity(like each product, customer, or order) inside the loop as a **Success** or **Failure**.
This can be viewed by clicking the "View" button in the Logs section.
### Options
* ***Status*** - Status of the execution. Success or Failure
* ***Entity ID*** - ID of the entry. Useful in identifying if the entities succeeded or failed. Example*:* `{{2.item.product_id}}`
* ***Short Message*** - Content to be logged. Keep it short and readable.
* ***Detailed Message*** - Log request or response information in more detail, in case of failures. Otherwise, avoid logging large data as it might slow down the logs page.
### Examples
**Success Entity Use Case**
* Status: `Success`
* Entity ID: `{{2.item.product_id}}`
* Short Message: `Product {{2.item.product_id}} Created`
* Detailed Message: Empty. As it is not needed.
**Failure Entity Use Case**
* Status: `Failure`
* Entity ID: `{{2.item.product_id}}`
* Short Message: `Product ID: {{2.item.product_id}}, Error: {{2.item.error_message}}`
* Detailed Message: `{{2.item}}`
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dckapintegrator.com/project-manager/workflows/actions/detail-logger.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
