# Sync warnings

### Overview

You can set warnings and alerts to monitor sync successes and failures. DinMo supports sending alerts via Slack and email. Warnings can be set as default for all syncs of a specific destination or at the individual sync level.

### Warning types

DinMo offers different types of sync warnings.

* **Activation failure**: This alert will be triggered when an activation is not correctly sent to the destination (<mark style="color:red;background-color:red;">failed</mark> status for the entire sync). You'll get more information on the reasons for sync failure at overview level (insufficient credentials, missing source data, etc.).
* **Percentage of rejected rows**: This warning will be triggered when a certain percentage of data has been refused on the destination side. This feature is useful when you expect that a certain number of rows may fail, and you don't want to be notified unless the number of errors is significant.
* **Jobs with no operations**: This warning will be triggered when several runs have been made, without loading any data at the destination. Occasionally, some jobs will send no data at all (i.e. there has been no data update between the two jobs). However, if this situation persists, the behavior may not be normal and the segment may be broken. This feature alerts you to such cases!

If you wish, notifications can all **be sent by e-mail and/or slack**. In all cases, warnings will be available in DinMo at several locations on the platform.

{% hint style="warning" %}
To receive Slack sync notifications, you must connect Slack upstream in DinMo's general settings.\
\
:point\_right: To find out more, consult [this section](https://docs.dinmo.io/workspace-management/set-up#setting-up-alerts).
{% endhint %}

### Configuration

Sync-specific warnings can be configured at the **destination level** (and will therefore be applied by default to all activations using this destination) or **at the level of a specific sync**.

{% hint style="info" %}
Alerts for complete sync failure must be configured in workspace settings.\
\
:point\_right: To find out more, consult [this section](https://docs.dinmo.io/workspace-management/set-up#setting-up-alerts).
{% endhint %}

1. **At the destination level**

When a destination is created, DinMo suggests configuring *default activation settings* for all destinations that support it.

At the bottom of the configuration page, DinMo lets you create warnings for this destination.

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2Fye4AHLThIWlNea7AFwqQ%2Fimage.png?alt=media&#x26;token=9bf898c9-21ce-4fb3-a8f1-5d072f30e866" alt=""><figcaption><p>How to — Set up sync warnings at the destination level</p></figcaption></figure>

2. **At the sync level**

When configuring an activation, you must:

* Choose the segment that must be synchronised with your destination
* Choose the destination that will receive the data
* Configure your activation

At the bottom of the configuration page, DinMo lets you create warnings for this sync.

{% hint style="success" %}
If you have created *default activation settings*, but do not wish to apply them to a specific activation of this destination, you can always click on “Advanced configuration”.
{% endhint %}

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2FZ1h4IW6LKhvKmJ762QEn%2Fimage.png?alt=media&#x26;token=34686342-30dd-4a03-b684-1b2dbdcf944a" alt=""><figcaption><p><em><strong>Advanced configuration</strong></em> allows you to modify the warnings for a specific sync, without modifying all the <em>default activation settings</em>.</p></figcaption></figure>

{% hint style="info" %}
No matter where you decide to set up your warnings, **you'll be asked for the same information**, which we detail below.
{% endhint %}

When creating *Warnings*, you will be encouraged to choose the type of alert you want, between *Percentage of rejected rows* or *Jobs with no operations*.

#### Percentage of rejected rows

If you choose *Percentage of rejected rows*, then you'll also have to choose the percentage above which you want to be alerted and the means of alert communication (email/slack).

:point\_down: In the example below, you will be notified as soon as the number of rows rejected by the destination or DinMo exceeds 10% of the total number of rows.

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2FGmGZOEqLWo60WNuv5j9d%2Fimage.png?alt=media&#x26;token=ef04c500-488b-4f85-aa69-b41784a6a816" alt="" width="563"><figcaption><p>Warning and email alert if the percentage of rejected rows is higher than 10%</p></figcaption></figure>

#### Jobs with no operation

If you choose *Jobs with no operation*, then you'll also have to number of jobs without operation above which you want to be alerted and the means of alert communication (email/slack).

:point\_down: In the example below, you will be notified as soon as the number of jobs with no operation is higher than 3.<br>

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2F776VGP9wcKjWPvwBH2Hm%2Fimage.png?alt=media&#x26;token=9669b189-f3fb-4cce-8377-79d6e8b66b52" alt="" width="563"><figcaption><p>Warning and email alert if the number of jobs without operation is higher than 3</p></figcaption></figure>

### Where to check warnings?

If you have selected the option to be alerted by e-mail or Slack, you will receive specific communications on these channels.

{% hint style="info" %}
You will receive maximum 1 notification per alert configuration per 24h.
{% endhint %}

In all cases, warnings are also available directly on the platform:

* In the **Control Center**

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2FvUHCMxu7QcS4jcwDqtrA%2Fimage.png?alt=media&#x26;token=099d72c9-6625-441f-a074-99ea58fdfa32" alt="" width="318"><figcaption></figcaption></figure>

* In the **Activation List**

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2FFDKSV0kxircitnXuAX8r%2Fimage.png?alt=media&#x26;token=8d12da5c-8005-4c79-b947-18ddd6905e4c" alt=""><figcaption></figcaption></figure>

* In the **Activation Overview**

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2FQ1SobyMS2xCRqLQUYD56%2Fimage.png?alt=media&#x26;token=972a3f7e-aa6c-4814-89c7-70257b85f446" alt=""><figcaption></figcaption></figure>

* In the **Activation run history**

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2FMWZnFQM6Ltx2faCqyZdO%2Fimage.png?alt=media&#x26;token=6a9238be-9c67-4ca4-8868-630d62d932b1" alt=""><figcaption></figcaption></figure>

Of course, as soon as the problem is solved, the **warning disappears from the application**.