> 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/editing-removing-scheduled-run-times-for-a-macro.md).

# Editing/Removing Scheduled run times for a Macro

### Introduction

This procedure details how to change or remove the date and/or time a macro is scheduled to run. To perform this procedure you need the "Schedule & Run Macros" operator privilege.

### 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 edit or remove.
3. **Right click** the mouse button, and select **Properties**.
4. Click the **Schedule** tab.
5. Do you want to edit or remove a scheduled run time?

   <table><thead><tr><th width="96">If...</th><th>then...</th></tr></thead><tbody><tr><td>edit</td><td>select the "Occurrence Time", and edit the date and/or time from the Date drop-down box and/or Time Box as appropriate.</td></tr><tr><td>remove</td><td><strong>right click</strong> on the "Occurrence Time" and select <strong>Remove from List</strong>.</td></tr></tbody></table>
6. 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

The scheduled run time has either been changed or removed from the macro. If the run time was changed, the operator's name in the "Last Modified By" field would also be changed to the current operator's name.


---

# 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/editing-removing-scheduled-run-times-for-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.
