--- title: "Configuring the Copp Clark schedule to import calendars" slug: "configuring-the-copp-clark-schedule-to-import-calendars" tags: ["horizon", "calender", "market holiday data", "copp clark"] updated: 2024-10-23T11:20:26Z published: 2024-10-23T11:20:26Z canonical: "support.lusid.com/configuring-the-copp-clark-schedule-to-import-calendars" deprecated: true --- > ## Documentation Index > Fetch the complete documentation index at: https://support.lusid.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring the Copp Clark schedule to import calendars > **Deprecated.** Configuring **Horizon: Copp Clark** via Scheduler is now deprecated. If you are setting up **Horizon: Copp Clark** for the first time, we recommend [following these instructions to configure Horizon: Copp Clark using the Integrations dashboard](/v1/docs/configuring-horizon-copp-clark-to-import-calendars-using-the-integrations-dashboard). If you currently use Scheduler to maintain **Horizon: Copp Clark**, please [contact support](https://www.finbourne.com/contact) for assistance on migrating to the Integrations dashboard. LUSID’s Copp Clark integration runs a schedule daily in your domain to provide you with the latest market holiday data. - On Day 1, you *must* configure the schedule to import at least one calendar and then [enable the schedule](/v1/docs/enabling-the-copp-clark-schedule). - Subsequently, you *can* reconfigure the schedule at any time to import different calendars. ## Configuring the Copp Clark schedule arguments You can configure the schedule to: - Import Copp Clark calendar types, such as Payment Systems, Financial Centers, Exchange Trading and Exchange Settlement. - Import only a subset within these calendar types, or remove some of these calendar types or subsets. To do this: 1. Sign in to the [LUSID web app](https://www.lusid.com/app) using the credentials of a LUSID administrator. 2. From the top left menu, select **Jobs & Scheduling > Schedules**: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/040646a7-2192-4347-a9c4-b3ab1f4370c4.png) 3. In the **Schedules** page, select **Menu** on the Copp Clark schedule and then **Edit**: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/9f2e87a9-da46-4a15-9751-2eb392d3825e.png) 4. Select **Next** on the **Specify Job** tab to reach the **Arguments** tab: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/a09dd4c5-9303-4231-8417-444dc5bbb3ef.png) Here you can configure the arguments (using the table below as a guide) to determine which data is imported into your LUSID domain when the schedule next runs: | **Calendar type** | **Argument name** | **Value** | **Imported calendar code** | | --- | --- | --- | --- | | Currency FX Markets | `--calendars` | `Currencies` | `<ISO>__C` | | `--accepted-currencies` | ISO codes for required currencies e.g. `AUD,GBP,USD` | | Payment Systems | `--calendars` | `PaymentSystems` | `<ISO>__P` | | `--accepted-currencies` | ISO codes for required payment systems e.g. `AUD,GBP,USD` | | Financial Centers | `--calendars` | `FinancialCentres` | `<LOCODE>__B` | | `--financial-centre-codes` | `LOCODE` (default), `FpML` or `FpML,LOCODE` | | `--accepted-financial-centres` | LOCODEs and/or FpMLs for required countries/cities separated with `/`, `-`, `_` or nothing, e.g. `AU/SYD,GB-LON,USNYC,KR_SEL` > **Note:** Coverage for FpML is smaller than coverage for LOCODE. We recommend including LOCODE if you want to be sure all business centres are covered. | | Exchange Trading | `--calendars` | `ExchangeTrading` | `<ISOMIC>__T` | | `--accepted-exchanges` | ISO Market Identifier Code for required exchanges e.g. `XASX,XLON,XNYS,XSTU` | | Exchange Settlement | `--calendars` | `ExchangeSettlement` | `<ISOMIC>__S` | | `--accepted-exchanges` | ISO Market Identifier Code for required exchanges e.g. `XASX,XLON,XNYS,XSTU` | For example, we can set the `--calendars` argument to `Currencies` and `--accepted-currencies` to `AUD,GBP,USD` to request the schedule only imports data for the AUD, GBP and USD Currency FX Markets: Note the following: - You can specify multiple `--calendars` values by separating each value with a comma and no space, e.g. `PaymentSystems,FinancialCentres,ExchangeTrading`. - Values for `--accepted-…` should be comma-separated with no spaces and are case-insensitive. ## Understanding calendar codes and which calendar type your data originates from Some calendar types take in the same identifiers: - `Currencies` and `PaymentSystems` both use ISO codes and *could* import two calendars with the same code, e.g. `AUD` - `ExchangeSettlement` and `ExchangeTrading` both use ISO MICs and *could* import two calendars with the same code, e.g. `XASX` To help you know exactly which calendar data you are using, each imported calendar code is *qualified* (that is, suffixed) with a letter that identifies which `--calendars` type the data comes from. The qualifying letter for each calendar is: | **Calendar type value** | **Code suffix** | **Example** | | --- | --- | --- | | `Currencies` | `__C` | `AUD__C` | | `PaymentSystems` | `__P` | `AUD__P` | | `FinancialCentres` | `__B` | `AU/SYD__B` | | `ExchangeTrading` | `__T` | `XASX__T` | | `ExchangeSettlement` | `__S` | `XASX__S` | We recommend using *qualified* calendars to avoid confusion with your dataset, but you can choose to import your market holiday data *unqualified* by configuring the following arguments: - For `Currencies` calendars, set the `--unqualified-iso-currency` argument value to `Currencies`. This imports two of each calendar with codes `<ISO>__C` and `<ISO>`. - For `PaymentSystems` calendars, set the `--unqualified-iso-currency` argument value to `PaymentSystems`. This imports two of each calendar with codes `<ISO>__P` and `<ISO>`. - For `FinancialCentres` calendars, set the `--unqualified-locode` and/or `--unqualified-fpml` arguments to `FinancialCentres`. This imports two of each calendar with the codes `<LOC/FPML>__B` and `<LOC/FPML>`. - For `ExchangeTrading` calendars, set the `--unqualified-iso-mic` argument value to `ExchangeTrading`. This imports two of each calendar with the codes `<ISOMIC>` and `<ISOMIC>__T`. - For `ExchangeSettlement` calendars, set the `--unqualified-iso-mic` argument value to `ExchangeSettlement`. This imports two of each calendar with the codes `<ISOMIC>` and `<ISOMIC>__S`. ## Troubleshooting a failed schedule You can check the status and configuration of every schedule that has run by navigating to **Jobs & Scheduling > History** from the top left menu in the [LUSID web app](https://www.lusid.com/app): If you configure the Copp Clark schedule to import a large volume of data (e.g. all calendars from all calendar types), you may find the schedule fails with the following error message: You can split the data import into multiple schedules, such as creating one schedule per calendar type, to alleviate this issue. To do this: 1. From the top left menu in the [LUSID web app](https://www.lusid.com/app), navigate to **Jobs & Scheduling > Jobs**: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/6b6ccc39-ec0c-40c8-a311-39addbad2171.png) 2. In the **Jobs** page, select the **Menu** icon on the Copp Clark job then select **Create a schedule**: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/7c8d0855-1fac-4634-a355-aeb8cf8d04e2.png) 3. Specify a **Scope**, **Code**, **Schedule name**, and **Description** for your schedule: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/f8d6ea9f-4062-4e36-ae19-8a8eecbe0985.png) 4. You can then configure the [**Optional Arguments**](/v1/docs/configuring-the-copp-clark-schedule-to-import-calendars#configuring-the-copp-clark-schedule-arguments) and [**Triggers**](/v1/docs/configuring-the-copp-clark-schedule-to-import-calendars-at-different-days-and-times) as usual and click **Save** to create your new schedule. If a schedule fails and the steps above do not resolve the issue, [contact Technical Support](https://www.finbourne.com/contact).