> 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/command-centre-client/configuring-command-centre/creating-reports/scheduling-a-report.md).

# Scheduling a Report

All reports configured in Command Centre Client, (i.e. Activity, Cardholder, Evacuation, Time, Voltage and Access reports) can be scheduled to run at specified times, as follows:

1. Click the **Schedule/Macro Output** button.

   The Schedule/Macro Output pop-up displays, which allows you to configure a report to be run at either scheduled or ad hoc times.

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

   **Note:** Changing the destination type in the **Send To** drop-down list changes the controls that display in the 'Schedule and Macro Output' section of this pop-up. This example shows the fields that display when 'Email' is selected.
2. Do you want the report to be run at multiple explicit times or repeat times?

   <table><thead><tr><th width="207">If the report is to be run at...</th><th>then...</th></tr></thead><tbody><tr><td>multiple explicit times,</td><td><ol><li>Click the <strong>Run at</strong> radio button.</li><li>Enter a date and time, and click the <strong>Add</strong> button.<br>The date and time appears in the <strong>Next Scheduled Run Times</strong> grid.</li><li>Repeat Steps a - b for each explicit time you require.<br><br><strong>Note:</strong> If you click the <strong>Repeats</strong> radio button, then the explicit additions are removed from the <strong>Next Scheduled Run Times</strong> grid.</li></ol></td></tr><tr><td>repeat times,</td><td><ol><li>Click the <strong>Repeats</strong> radio button.</li><li>Select the 'initial' <strong>From</strong> date and time.</li><li>Select an <strong>Until</strong> date and time if required.<br><br><strong>Note:</strong> If no <strong>Until</strong> date is entered, the report will repeat indefinitely.</li><li>Select the regularity for the report to be run, (i.e. <strong>Every</strong> one or many <strong>Hours</strong>, <strong>Days</strong>, <strong>Weeks</strong> or <strong>Months</strong>).<br><br><strong>Note:</strong> When <strong>Weeks</strong> is selected from the drop-down list, the days of the week display with an ability to select one or multiple days, (e.g. Monday and Thursday).<br>The next five dates and times appear in the <strong>Next Scheduled Run Times</strong> grid.</li></ol></td></tr></tbody></table>
3. Click the appropriate option from the **Send To** drop-down list for where you want the report to be generated:

   <table><thead><tr><th width="109">Select...</th><th>if you want to...</th></tr></thead><tbody><tr><td>Printer</td><td>print the information to a selected <strong>printer</strong>, and type in the printer name.</td></tr><tr><td>File</td><td>save the information to <strong>file</strong>. Select the required file type for the report from the <strong>Format</strong> drop-down list, and type in the file location and name. You can also append the date and time to the file name if required, by checking the <strong>Append date/time</strong> checkbox.<br><br><strong>Note:</strong> Selecting the 'Export images' option from the <strong>Format</strong> list will output report images as individual files and export the report itself as a CSV file. If you select this option, an additional field displays:<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-35f5ed6ea3c2b1d8dd1547082ebe153acb688c88%2Fexportimagesformat.png?alt=media" alt=""><br>By clicking the <strong>Default naming style</strong> button, a Choose file names pop-up displays.<br>Go to Step 3 of <a href="https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/reports/exporting-cardholder-images.md">Exporting Cardholder Images</a> for the full procedure.<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-64fecba91221f9da9ea23b37669f2f84f29cd248%2Fchoosefilenames_popup.png?alt=media" alt=""><br></td></tr><tr><td>Email</td><td><ol><li><p>select Cardholders and/or manually enter email addresses to receive the emailed Report, as follows:<br><strong>Selecting Cardholders:</strong><br>Click the <strong>Select Cardholders</strong> button and use the browse tool to search for the required cardholders.<br><strong>Notes:</strong></p><ul><li>Emails will only reach the cardholder if the Notification flag is enabled for that email address PDF.</li><li>If a selected cardholder has more than one email address, the 'first' one displays, with the string ',...' (indicating they have more than one).</li></ul><p><strong>Manually entering email addresses:</strong><br>Click the <strong>Add Email Address</strong> button and enter the required email address in the free-text pop-up that displays. Click the <strong>Add</strong> button, and either enter additional email addresses or click the <strong>Close</strong> button.<br><strong>Note:</strong> Only the email address will display, and the Cardholder Name will be left blank.</p></li><li>Select the required file type for the report from the <strong>Format</strong> drop-down list.<br><strong>Note:</strong> Email addresses display here as 'Read-only'.</li></ol></td></tr></tbody></table>
4. A report run from a schedule or a macro will run as if being run by the last operator to save the report. This operator name displays as 'read-only' in the **Run As** field.

   **Note:** If Operator 1 creates and saves a report and assigns it a schedule (or it is run from a macro), the report will 'Run as' Operator 1. If subsequently Operator 2 edits and saves the same report, the report will then 'Run as' Operator 2.
5. Click the **OK** button.

   The Report Schedule is saved.

   **Note:** An operator may choose to cancel the schedule by selecting the **Cancel** button, or to remove the schedule by clicking the **Delete Schedule** button.

### Hints

{% hint style="info" %}
The following table provides some error messages that can appear if a scheduled report fails, and what can be done to resolve the problem.

<table><thead><tr><th width="292">Error Message</th><th>Solution</th></tr></thead><tbody><tr><td><em>"PrintTicket provider failed to bind to printer. Win32 error: -2147467231"</em></td><td>If the scheduled report fails with this error you will need to download and apply a patch from Microsoft.<br>Please refer to Microsoft Article ID: 2954953.</td></tr><tr><td><em>"PrintTicket provider failed to bind to printer. Win32 error: Access is denied"</em></td><td><p>This error means the logon account for the FT Command Centre service does not have privileges to the printer.<br>Perform the procedure below to change the logon account. From v7.70 onward you need to use the Recovery Code when changing the logon account.</p><ol><li>Make sure you have a recovery code, make a new one if necessary while logged on.</li><li>Change the FT Command Centre Service login (using <strong>services.msc</strong>) to your domain name\user and password (or local user and password if not on a domain).</li><li>Go off the domain (onto a workstation) and then back on the domain.</li><li>Using <strong>CCFTRecoveryCode.exe</strong>, apply the existing recovery code again.<br>Services will start. You can now schedule printing.<br>This applies to both network and local printers.</li></ol><p><strong>Note:</strong> If you change the FT Command Centre Service login to a user who is a standard user (not an administrator) you will not be able to schedule printing.</p></td></tr></tbody></table>
{% endhint %}


---

# 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/command-centre-client/configuring-command-centre/creating-reports/scheduling-a-report.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.
