> For the complete documentation index, see [llms.txt](https://docs.monitorss.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monitorss.xyz/configuration/bot-configuration/schedules.md).

# Schedules

A custom schedule is a way to put feeds with certain specified words in their links on a separate schedule from everything else. Every schedule is defined in a file named settings/schedules.json. For example:

{% code title="settings/schedules.json" %}

```javascript
{
    "feed43": {
        "refreshRateMinutes": 100,
        "keywords": [
            "feed43",
            "feed43.com"
        ]
    },
    "some other one": {
        "refreshRateMinutes": 1000,
        "keywords": [
            "whatever.com"
        ]
    }
}
```

{% endcode %}

Keywords is an array of words that the links must include. Note that this is done with the function `<string>.includes`. This means that if you `"a"` into the keywords array, it will trigger all links that has the letter `a` in it.

Any links assigned to a custom schedule (the assignment of links to custom schedules is logged on initialization, specifying what link is assigned to what schedule) will be excluded from the default schedule. If more than one schedule's keywords matches a feed link, whichever schedule gets to it first will 'claim' it.

You can also specify feeds by their IDs:

{% code title="settings/schedules.json" %}

```javascript
{
    "feed43": {
        "refreshRateMinutes": 15,
        "feeds": [
            "id123"
        ]
    }
}
```

{% endcode %}

To get feed IDs, you may use the `backup` command by looking for the `_id` key in objects within the  `feeds`  array.


---

# 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://docs.monitorss.xyz/configuration/bot-configuration/schedules.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.