> 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/stopping-an-interface.md).

# Stopping an interface

### Introduction

Only an interface that is currently running can be stopped.

When an interface is stopped an event is generated. This event shows when the interface was stopped and by whom.

**Notes:**

* If a manually run interface with multiple import files is stopped, the other files will not be processed.
* If a scheduled interface with multiple import files is stopped, the next file will be processed at the next scheduled time, unless the interface is disabled. If an interface that belongs to a sequence, with multiple files is stopped, the next interface in the sequence will not run, until such time as the previously sequenced interface has completed.
* When an interface is stopped the source file will be moved to the completed folder. Failed and un-processed cardholder records will be copied to a new file and placed in the failed folder. The log file details all un-processed cardholder records.

### Procedure

1. Click **Manage** from the menu bar.
2. Click **Enterprise Data Interface**.

   The Enterprise Data Interfaces list window opens.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c33dfb7cdd33ff2b0d18f43b25ec759145deec51%2Fstopinterface.png?alt=media)
3. Select the Enterprise Data Interface you wish to stop.
4. Click the **Stop** button.


---

# 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/stopping-an-interface.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.
