> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/activations/troubleshooting-syncs/automatic-pause-or-resume-activations.md).

# Automatic pause or resume Activations

Objects used in DinMo can be modified or deleted (inside or outside DinMo), affecting activations.

This is the case, for example, when a table used in a DinMo model is deleted from the source data warehouse.

To prevent runs being launched automatically (involving calculations and therefore additional costs at the level of the source), DinMo automatically stops these syncs until the problem has been solved.

## DinMo's system will automatically pause a activation and its related scheduled ones if:

* If DinMo cannot access the data source
* If a related entity is broken (source, model, calculated field, etc.)

## On the contrary, DinMo's system will automatically resume a sync and its related scheduled ones if the system has automatically paused a activation (see above) and:

* The source validation is completed without errors
* DinMo no longer detect errors on related entities

{% hint style="info" %}
All verification operations are performed nightly (between 12am and 2am CET) or whenever a user launches a manual test.
{% endhint %}

## How will the user know if the system has paused the activation?

* On the activation list stopped sync, there is an icon signaling that the activation has an issue.
* A tooltip indicates to the user that the system has automatically paused the activation and indicates what kind of entity is the culprit.

<figure><img src="/files/w76Qsoh4ekU6ZJct9QHk" alt=""><figcaption><p>Automatic pause because the model has been altered</p></figcaption></figure>


---

# 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.dinmo.io/activations/troubleshooting-syncs/automatic-pause-or-resume-activations.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.