> For the complete documentation index, see [llms.txt](https://help.defisaver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.defisaver.com/features/automation/when-are-automation-transactions-made.md).

# When are Automation transactions made?

Once you enable any specific automated strategy, Automation bots will constantly monitor your position moving forward in order to react and execute any needed transaction(s) as soon as your configured trigger (e.g. ratio or price point) is reached.

> The system checks all automated positions every minute in order to keep up with potentially quickly changing market conditions. \
> \
> However, it's important to keep in mind that your position's status is effectively decided by the oracles used by the protocol in question. Because of this, one can also say that Automation runs on oracles utilized by the protocol you're using.

In practice, automated adjustments will happen when:<br>

* Users adjusts their configuration (potentially to purposefully force an automated adjustment)
* The price of the used asset changes enough that the user configured ratios or price thresholds are reached.

In terms of different price oracles used in different protocols, these are:<br>

* **Maker OSM** (short for Oracle Security Module) **is used by MakerDAO and Reflexer**. \
  \
  The OSM is best known for its 1-hour update delay, where the prices in the protocol are updated only once every full hour with each next price update also known a full hour in advance. \
  \
  You can check current and next price updates in MakerDAO using platforms such as [DeFi Explore](https://maker.defiexplore.com/stats) and [DaiStats](https://daistats.com/#/oracles), though these are also shown in our [Maker dashboard](https://app.defisaver.com/makerdao/).<br>
* **Chainlink oracles are used by most other protocols, which includes Aave** (v1, v2 and v3)**, Compound** (v2 and v3), **Liquity, Morpho and Euler v2.** \
  \
  You can check the status of all Chainlink feeds on their [Data Feeds](https://data.chain.link/) page and their current prices are also shown in all of the dedicated protocol dashboards at DeFi Saver.<br>
* Some protocols use custom-built oracles, such as **Fluid** and **LlamaLend.**

***

## Related Articles:

* [How does Automation work?](https://help.defisaver.com/features/automation/how-does-automation-work)
* [Automation](https://help.defisaver.com/features/automation)
* [Use-case](https://help.defisaver.com/features/automation/use-case)


---

# 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://help.defisaver.com/features/automation/when-are-automation-transactions-made.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.