> For the complete documentation index, see [llms.txt](https://ontime.gitbook.io/v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ontime.gitbook.io/v2/features/the-delay-workflow.md).

# The delay workflow

The delay workflow is thought of a way to control schedule delays in realtime. Few notes:

The delay information is added as an overlay to warn backstage users that the event rundown schedule has changed without affecting any of the publicly available screens.

{% hint style="warning" %}
Delays only show in backstage screens, no delay information is show in the public screens
{% endhint %}

![Events 6 and 7 have been delayed by 15 minutes](/files/veQB1UXC5I7syleNHPMT)

Looking at the image above, we see that a delay event with a value of 15 minutes causes events 6 and 7 to have a delay. The delay is stopped by a block event and event 8 runs as normal.

![Closer look at the delay and the event, note the yellow marks and the two timer indications](/files/TxaglrsTmawLJPynWTBR)

As shown in the image above, event 6 has been delayed by 15 minutes. This is visible with the *+15* indication on the left. 

The timer also has two indications now, *09:55* and *10:10* (for the start time): meaning the original time of 09:55 has been delayed and is now 10:10. The delayed times have a light orange outline

Using *Apply Delays* function (orange button with double chevrons down), we can apply the change in times permantely


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ontime.gitbook.io/v2/features/the-delay-workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.