> 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 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.appstrategy.com/apprules-r-documentation/samples/sample-projects/miscellaneous/target-activity-errors-and-logs.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.