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

# Scheduling an interface

### Introduction

**Note:** Functionality specific to scheduling an interface is only available if your site is licensed to schedule interfaces.

When an interface has been scheduled and enabled, it will run according to the schedule without operator intervention.

You can schedule an interface to run once a day, or run on a regular basis, (e.g. every hour). This will ensure Gallagher Command Centre is regularly updated with the latest data.

If you configure your third party application to provide the source file on a regular basis, you can then schedule an interface to "pick-up" and import the source file when it is provided.

**Notes:**

* Only the first interface in a sequence can be scheduled. All other interfaces added to a sequence cannot be scheduled.
* If you configure your third party application to provide the source file on a regular basis, you can then schedule an interface to "pick-up" and import the source file when it is provided.
* If an interface is scheduled to run and there is no source file, the interface will not run until the next scheduled time.
* When scheduling an interface to run on an interval, the hours and minutes specify how often Gallagher Command Centre checks for a file to import, or connects to the database server.
* If an interface is scheduled to run and the interface is unable to connect to the database server, the interface will not run until the next scheduled time.
* If an interface is scheduled to run from a database, the interface will process the records as present in the database, at that time.
* If you are running a large import operation, it is recommended you schedule the import to run at a time when Gallagher Command Centre is at its least active, (e.g. late at night, during a weekend or during a public holiday).
* Scheduled interfaces are single threaded, meaning the interface will run one import operation after another via the schedule. You will need to ensure you configure your schedule to give the previous import enough time to complete, before the next import is scheduled to run. If the scheduled interface is at the start of a sequence, you will need to ensure you configure your schedule to give all interfaces in the sequence enough time to complete, before the next import is scheduled to run.
* If an interface has been scheduled to run on an interval and you have not specified a start and end date, the interface will continue to run according to the schedule until it is disabled.

### Procedure

1. Click the **Schedule** tab.

   This tab displays the schedule configured for this interface.

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

   **Note:** If your site is not licensed to schedule interfaces this tab will be grayed out.
2. Check the **This integration runs on a schedule** checkbox.

   **Note:** If the interface forms part of a sequence a confirmation dialog window opens.
3. If you wish to run the import once a day:
   1. Select **Run continuously**.
   2. Select **Run once a day** and enter the time of day you require the import to run.
4. If you wish to run the import once a day, between specific dates:
   1. Select **Run between theses dates**.
   2. Select the **Start date** and **End date** you require the import to be run between. The End date must be greater than or equal to the Start date.
   3. Select **Run once a day** and enter the time of day you require the import to run.
5. If you wish to run the import more than once a day:
   1. Select **Run continuously**.
   2. Select **Run on an interval**.
   3. Enter the **interval**, (e.g. run every 2 hours and 30 minutes).
   4. Enter the **Starting at** time. Importing will start at this time each day.
   5. Enter the **Ending at** time. Importing will end at this time each day.
6. If you wish to run the import more than once a day, between specific dates:
   1. Select **Run between these dates**.
   2. Select the **Start date** and **End date** you require the import to be run between. The End date must be greater than or equal to the Start date.
   3. Select **Run on an interval**.
   4. Enter the **interva** l, (e.g. run every 2 hours and 30 minutes).
   5. Enter the **Starting at** time. Importing will start at this time each day.
   6. Enter the **Ending at** time. Importing will end at this time each day.


---

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