> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/scheduling/scheduling_events.md).

# Scheduling

Available Event Types in scheduling.

### Command

Select a Command to be executed by the Player at a specific point in time

### Overlay Layout

Layouts that have been designed as an Overl ay Layout will be scheduled at the same time as existing Layouts to create an overlay of content when displayed.

### Interrupt Layout

An Interrupt Layout will schedule a selected Layout to play **in-between** other Layouts in the 'usual schedule'.

Xibo will work out when it will be played using how many **seconds per hour** or as a **Percentage** entered on the schedule.

{% hint style="success" %}
This can be useful if you have Announcements that need to be shown for a particular amount of time within the usual schedule! 
{% endhint %}

* Select **Interrupt Layout** as the Event Type from the drop down menu when adding an Event.
* Complete the form fields to create the schedule.

#### Share of Voice

Enter the amount of time the Layout should be shown in seconds per hour or as a percentage (0 - 100%) of the events duration (the difference between the from date and the to date) that the **Interrupt Layout** should occupy the usual schedule.

{% hint style="warning" %}
If your 'main' Layout has a long duration, the Interrupt Layout may show in a block in order to satisfy the SoV criteria entered!
{% endhint %}

### Action

**Scheduled Actions** listen for a Trigger Code coming in on a webhook to Navigate to a Layout or to run a Command.

* **Navigate to Layout** - enter the code identifier for the Layout the Player should navigate to when triggered. This code is created when adding a new Layout or from editing an existing from the Layouts grid.
* **Command** - select the Command to run.

## Synchronised Events

Synchronised Events are used in conjunction with Sync Groups to show mirrored or a video wall configuration across 2 or more Displays.

{% hint style="warning" %}
Ensure you have created and configured a **Sync Group** prior to scheduling!
{% endhint %}

Click on the **Add Synchronised Event** button at the top of the schedule grid to open the **Add Synchronised Event** form.

Select a Sync Group from the drop down menu.

* Use the **Layout** drop down to select which content should be shown on each Display within the group.

When selecting different content to show in a wall configuration on Displays, the total duration will be enforced by the content on the Lead Display.

{% hint style="info" %}
The Lead Display will issue instructions to change the sequence based on its assigned content. Please bear in mind that other Displays within the group could fall out of sync if their content is not similar in design (same number of items, durations etc).
{% endhint %}

* Select **Mirror** to automatically set the same item on each Display within the group automatically.

{% hint style="success" %}
Sync Playlists on different Layouts by using a **Content Synchronisation Key**!
{% endhint %}

### Dayparts

* Events are scheduled using **Dayparting** information:
  * Select **Custom** to enter your own start and end times. Use the **Relative time** checkbox to input the Hours and Minutes when creating a Scheduled Event (not available for Synchronised Events).
  * Select **Always** to have the content always scheduled on the selected Display.

{% hint style="success" %}
Create your own defined Dayparts to select for even easier scheduling!
{% endhint %}

* Use the drop down to select what needs to be scheduled from the list.


---

# 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.xibosignage.com/scheduling/scheduling_events.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.