> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/autosync-for-mim/configuration/triggers/scheduled-interval-trigger.md).

# Scheduled interval trigger

#### Summary

AutoSync has built-in support for triggering a run profile at a regular interval starting at a particular day or time. For example, you can use the scheduled interval trigger to perform a full sync every Sunday at 3am.

If you need to run a profile repeatedly, without concern for the specific time it starts (eg every 15 minutes) then use the [repeating interval trigger](/autosync-for-mim/configuration/triggers/repeating-interval-trigger.md) instead.

#### Configuration

This trigger is available to use on any MA. From the triggers page, select `Add trigger...` and the scheduled interval trigger will be available from the drop down list. Each management agent can have an unlimited number of scheduled interval triggers.

![](https://2216211724-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXaBwZ6mZ5WbX108JiSsn%2Fuploads%2Fgit-blob-b97d79a58027c4a8c901c924cae984395e08878c%2Fscheduled-interval-trigger.png?alt=media)

| Setting                             | Description                                                                                                                                                                                           |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Run profile                         | The run profile to execute                                                                                                                                                                            |
| Trigger the run profile every       | The amount of time which must pass before the run profile is triggered                                                                                                                                |
| Starting from                       | The day and time to start the execution on                                                                                                                                                            |
| Run profile must be run exclusively | If this box is checked, then when this profile is triggered, AutoSync prevents any new jobs from starting, it waits for all existing jobs to finish, runs the job, and then resumes normal operations |

Note, that while you can specify a multi-step run profile, it is always best practice to specify single-step run profiles, and let AutoSync determine what follow up actions are required.


---

# 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.lithnet.io/autosync-for-mim/configuration/triggers/scheduled-interval-trigger.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.