> 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/site-installation/macros/scheduling-a-macro.md).

# Scheduling a Macro

### Introduction

To be able to schedule macros requires the "Schedule & Run Macros" operator privilege (a separate privilege from running a macro), because the ability to schedule macros means an operator could potentially unlock secure areas after hours, allowing unauthorised people access.

This procedure details how to schedule the date and time for a macro to run.

### Procedure

1. Click **Configure** from the menu bar, then **Macros**.

   The **Macro** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. Highlight the macro you want to schedule.
3. **Right click** the mouse button, and select **Properties**.
4. Click the **Schedule** tab.

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

   **Note:** If this macro was configured in the Command Centre Client with a schedule, rather than the Configuration Client, the grid (shown in the above screen shot) will not display. Instead, it will be replaced with the following message:

   **"Macro is on a repeating schedule and should be configured in Command Centre."**
5. **Right click** anywhere with the grid, (i.e. on a column header, on the scroll bar or in the blank area), and select **Insert**.

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

   A new entry is added to the grid and highlighted. This entry includes your name in the "Last Modified By" column and your workstation in the "Workstation" column.

   The Date and Time controls are enabled, and display the current date and time.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d7a5a0ade81c60ff0e02b07dbaf75ddc85411844%2Fnewmacro_scheduletab3.png?alt=media)
6. Do you want the macro to run today?

   If **yes**, go to Step 7. When you select the time, today's date will automatically default into the Occurrence Time column.

   If **no**, click the date drop-down list and select the date you want the macro to run, from the calendar displayed.

   **Note:** Dates and times in the past cannot be selected.
7. Alter the Time Box ![AlmZGeneralTab](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e4538d2407843d64dc424ee5b56ef583f213b62e%2Fmacro_timebox.png?alt=media) to the time you want the macro to run.

   The date and time display in the Occurrence Time column.
8. If you require this macro to run on other dates/times, repeat Steps 6 and 7 as necessary.

   **Note:**

   There is no limit to the number of times a macro can be scheduled to run.
9. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

A macro has been scheduled. The **Macro** List Window displays the next scheduled run time and the number of future run times for this macro.

**Note:**

Once a scheduled run time is reached and the macro is run, the entry is removed from the list on the **Schedule** tab.


---

# 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/site-installation/macros/scheduling-a-macro.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.
