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

# Manually running an interface

### Introduction

You can manually run an interface at any time. In order to run an interface the interface must first be enabled.

If an interface has been scheduled to run, but is unable to run because another scheduled interface is still running, you can use this feature to run the interface immediately.

**Notes:**

* When an interface is run, it will be run under the "Run as Operator" name.
* If an interface is running, it won't run again until it has completed running.
* If you manually run a scheduled or sequenced interface, it will still run according to its schedule or sequence.
* If you manually run an interface that forms part of a sequence, a dialog window displays allowing you to run all interfaces (from this point on) in the sequence, or only this interface.
* If an interface has been scheduled to run once a day, it can be manually run more than once in a day.

### 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-4d711cca6d80fa23ccdc392e317348d7fa83b2f5%2Fbookinginterfacemlw.png?alt=media)
3. Select the Enterprise Data Interface you wish to run.
4. Click the **Run Now** 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/manually-running-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.
