> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/samples/sample-projects/miscellaneous/target-activity-errors-and-logs.md).

# Target Activity Errors & Logs

This sample project demonstrates data record error tracking and logging on Target activities.  

 

* The activities in this sample project have been deliberately configured to generate data record errors. 

{% hint style="info" %}
Explore the MapRecordFields activity to see the invalid field mappings
{% endhint %}

* After running the project, use the **Logs/Stats** button to view **Project Run Details** for job statistics.
* Use the **Audit Logs** button from the Project Run Details toolbar to view additional statistics and the errored records and associated errors.

{% hint style="info" %}
You can experiment with the configurations and run the project to view the results as the project has been configured to use the embedded database.  No additional data source configurations are required.  
{% endhint %}


---

# 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.appstrategy.com/apprules-r-documentation/samples/sample-projects/miscellaneous/target-activity-errors-and-logs.md?ask=<question>&goal=<user_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.