> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/schedule-type-override-6182425.md).

# Schedule Type Override

Handling of endless *Schedule changes* on a Time Schedule [here](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-schedule-lines-6182445.md)

Setup can be:

* Overall level under CalculationID
* On the Time Schedule
* On the Time Schedule lines

Setup can be made for certain days or intervals of days, refer to the weekday field.

| Topic                         |
| ----------------------------- |
| [Calculation ID](#field-1)    |
| [Time Schedule](#field-2)     |
| [Weekday](#field-4)           |
| [Shift](#field-6)             |
| [Line No.](#field-10)         |
| [Schedule Type](#field-100)   |
| [Job Id](#field-110)          |
| [Activity](#field-111)        |
| [Job Description](#field-112) |
| [Schedule Type](#field-200)   |
| [Skip merge](#field-300)      |

## See also

## Reference

\
\\

<details>

<summary>Calculation ID</summary>

Related Calculation ID.

**Related topics**

* [Pay Export to Intect](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/payroll-exports/intect.md)

</details>

<details>

<summary>Time Schedule</summary>

Defines which Timeschedules the funktion works for.

* Empty - The line applies for all *Timeschedules*.
* Filled out - The line applies only for this *Timeschedule*.

</details>

<details>

<summary>Weekday</summary>

Defines which days the line will apply for. Default the field is filled out with "All days\*.

Options:

* Monday
* Tuesday
* Wednesday
* Thursday
* Friday
* Saturday
* Sunday
* All days
* Mon-Fri
* Sat-Sun

</details>

<details>

<summary>Shift</summary>

If the line only applies for a certain *Shift*, this must be filled out.

E.g. a Timeschedule with 3 *Shifts*

* Day - Shift 1
* Evening - Shift 2
* Night - Shift 3

</details>

<details>

<summary>Line No.</summary>

If the Schedule Change must setup on the "lowest level" (The individual line on the Timeschedule), this can be filled out.

</details>

<details>

<summary>Schedule Type</summary>

Fill out with the primary Scheduletype from the Timeschedule

E.G.:

* Break1
* Overtime
* Etc.

</details>

<details>

<summary>Job Id</summary>

Specified job/triggercode, that activates the "new" Schedule Type.

</details>

<details>

<summary>Activity</summary>

Specified job/triggercode, that activates the "new" Schedule Type.

</details>

<details>

<summary>Job Description</summary>

Specified job/triggercode, that activates the "new" Schedule Type.

</details>

<details>

<summary>Schedule Type</summary>

Fills out with a secondary Schedule Type the primary must be overrided with.

E.G.:

* CANCELBRK1 (Cancel break 1)
* Flex1

</details>

<details>

<summary>Skip merge</summary>

This field is only used for *Flexible Time Schedules*, where the format is *Time from Sign in*, usualy when there is a mark in *Merge Primary* on the break line.

</details>


---

# 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.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/schedule-type-override-6182425.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.
