> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/the-log-file.md).

# The log file

### Introduction

The log file can be used for troubleshooting purposes. The log file details the date and time the import started and completed.

The log file also lists all records that failed to be imported and provides a reason as to why each record failed.

When importing data from the source file, the log file is located in the completed folder directory and is named after the source file followed by the date and time of processing, (e.g. Student Data\_20091103\_114732.log).

When importing data from a database, the log file is located in the log folder directory and is named after the Data Source Name followed by the date and time of processing, (e.g. PERSONS\_V\_20121103\_114732.log).

### Rows shown in the log file

Each row in the log file displays the following data:

<table><thead><tr><th width="78">Row</th><th>Displays...</th></tr></thead><tbody><tr><td>First</td><td><ul><li>the date and time the import started</li><li>names the file imported</li></ul></td></tr><tr><td>Middle</td><td><ul><li>the date and time the record was processed</li><li>the record processed</li><li>a reason as to why the record failed</li></ul></td></tr><tr><td>Last</td><td><ul><li>the date and time the import completed</li><li>provides a summary of the import</li></ul></td></tr></tbody></table>

### Example

The following example shows a log file where the "Run as Operator" did not have sufficient privileges to import all cardholder records:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-57e5bbac30a9a0f76832b86f651d51512211f4d3%2Flogfile.gif?alt=media)


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/the-log-file.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.
