---
title: Connections and sync
description: How Advisor collects data from Cloudflare, the sync types, the schedule and the connection states.
updated: 2026-09-27
---

A connection is the read-only link between your tenant and a Cloudflare account. Through it, Advisor collects metrics, configuration, changes and DNS records.

## Connection states

| State | Meaning |
|---|---|
| **Conectada** (Connected) | Collection works normally. |
| **Pendente** (Pending) | The connection was created and has not finished its first collection. |
| **Erro** (Error) | The last attempt failed, for example because the token was revoked. Collection is paused until it is fixed. |
| **Desativada** (Disabled) | The connection is turned off and does not collect data. |

Currently, each tenant has one connection per provider.

## The four kinds of sync

| Kind | What it brings | Where it shows up |
|---|---|---|
| **Métricas** (Metrics) | Traffic, WAF and plans for the period | Overview, Zones, Traffic |
| **Postura** (Posture) | Zone security settings and rules; recalculates the score | Score, Risks, Consolidated posture |
| **Alterações** (Changes) | The log of who changed what in the Cloudflare account | Changes |
| **DNS** | Zone records and origin exposure probing. It is the slowest kind | Inventory, DNS records tab |

## When collection runs

- **First collection:** queued as soon as the connection is created. Metrics are backfilled up to 12 months.
- **Scheduled collection:** once a day at 02:00 (Brasília time), covering all four kinds. The time cannot be changed.
- **Manual sync:** go to **Integrações** (Integrations) > **Sincronizar** (Sync), pick the kinds and select **Iniciar sync** (Start sync).

:::availability
Manual sync requires the `connections.scan` permission, which is not part of the default tenant roles. Without it, data refreshes on the 02:00 collection. To get the permission, contact Guardnet.
:::

While a collection runs, Advisor shows **Sincronização em andamento** (Sync in progress), and the menu lists the kinds under **Sincronizando** (Syncing) and **Na fila** (Queued).

## Incomplete collection

A collection can finish without part of the data, for example when the token is missing a permission. The **Integrações** screen warns that "coleta(s) vieram incompletas" (collections came in incomplete) and the connection row shows **Coleta incompleta** (Incomplete collection) with the reason. Only the missing data is stale on screen. Everything else is up to date.

When the whole collection fails, the warning is "sincronização(ões) falharam" (syncs failed) and the connection moves to **Erro**.

## History kept

| Data | Window |
|---|---|
| Metrics on screen | 24 months |
| Cloudflare account changes | Up to 18 months (Cloudflare limit) |

To create the connection, refer to [Connect Cloudflare](/en/advisor/primeiros-passos/conectar-cloudflare/). Other time limits are in [Limits and time frames](/en/advisor/referencia/limites-e-prazos/).

---

> Guardnet Docs · https://docs.guardnet.com.br/en/advisor/conceitos/conexoes-e-sincronizacao/
> Documentation index: https://docs.guardnet.com.br/en/llms.txt