> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/engineering/skript-engine/skripte-konfigurieren.md).

# Configure scripts

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/8VOTgiTiOHTPCXWGaI1L/Script%20Engine.png" alt=""><figcaption></figcaption></figure></div>

<table data-full-width="true"><thead><tr><th width="99.79995727539062">Element</th><th width="219">Title</th><th>Details</th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Name</td><td>The name of the script.</td></tr><tr><td><strong>[B]</strong></td><td>Script language</td><td>Indicates the language in which the script is written (e.g. SQL, Python).</td></tr><tr><td><strong>[C]</strong></td><td>grid</td><td>Choose the intervals at which the script should be executed. <a href="#raster">↗ More information</a></td></tr><tr><td><strong>[D]</strong></td><td>Delay</td><td>Select how long the script execution should be delayed. <a href="#verzoegerung">↗ More information</a></td></tr><tr><td><strong>[E]</strong></td><td>Schedule</td><td>Choose whether the script should always run or only at certain times.</td></tr><tr><td><strong>[F]</strong></td><td>Description</td><td>A description of the script.</td></tr><tr><td><strong>[G]</strong></td><td>General configuration</td><td>If disabled, the configuration is hidden and the code window is displayed enlarged.</td></tr><tr><td><strong>[H]</strong></td><td>Delete</td><td>Removes the script. WARNING! This action cannot be undone.</td></tr><tr><td><strong>[I]</strong></td><td>Enable/Disable</td><td>Turns the script on or off without deleting it.</td></tr><tr><td><strong>[J]</strong></td><td>Code editor</td><td>Area for creating and editing the script.</td></tr><tr><td><strong>[K]</strong></td><td>Save</td><td>Saves the script with the changes made.</td></tr></tbody></table>

### grid

Using the grid, you specify the interval at which the script should run. The following values are available:

<table><thead><tr><th width="168">Element</th><th>Title</th></tr></thead><tbody><tr><td>M1</td><td>Script is executed every minute</td></tr><tr><td>M5</td><td>Script is executed every 5 minutes</td></tr><tr><td>M10</td><td>Script is executed every 10 minutes</td></tr><tr><td>M15</td><td>Script is executed every 15 minutes</td></tr><tr><td>M30</td><td>Script is executed every 30 minutes</td></tr><tr><td>H1</td><td>Script is executed every hour</td></tr><tr><td>H2</td><td>Script is executed every 2 hours</td></tr><tr><td>H4</td><td>Script is executed every 4 hours</td></tr><tr><td>H8</td><td>Script is executed every 8 hours</td></tr><tr><td>H12</td><td>Script is executed every 12 hours</td></tr><tr><td>Day</td><td>Script is executed every 24 hours at 00:00</td></tr><tr><td>Week</td><td>Script is executed once a week</td></tr><tr><td>Month</td><td>Script is executed once a month</td></tr><tr><td>Quarter</td><td>Script is executed once per quarter</td></tr><tr><td>Year</td><td>Script is executed once a year</td></tr><tr><td>Decade</td><td>Script is executed once every 10 years</td></tr><tr><td>Century</td><td>Script is executed once every 100 years</td></tr><tr><td>Event triggered</td><td>Script can be <a href="/collection/english-v14/documentation/alarme-regeln-und-eskalationen/regelketten/regelkette-konfigurieren.md#trigger">↗ rule chains</a> executed.</td></tr></tbody></table>

### Delay

The delay lets you further specify the time at which the script is executed. Script execution is delayed by the value (in seconds) entered in this field.

Example: For a script, the grid "Day" and a delay of "60" were selected. The corresponding script is executed daily at 00:01.


---

# 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://docs.buildings.ability.abb/collection/english-v14/documentation/engineering/skript-engine/skripte-konfigurieren.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.