Skip to main content

Monitor syncs and connection health

Once your datasets are syncing, the Dashboard and Activity tabs tell you whether the connection is healthy, what a sync did, and where it failed. This guide walks you through reading both.

Before you begin​

Steps​

  1. Go to Apps & Integrations → Airtable and open the Dashboard tab.

  2. Read the Connection card to confirm the account and its state. It shows:

    • Account — the connected Airtable account email (a dash when none is reported).
    • Status — a chip reading Connected, Needs reconnect, Error, or Disconnected. Anything other than Connected means outbound and inbound sync are interrupted until you reconnect on the Connect Airtable flow.
    • Automatic Sync — an Enabled or Disabled chip showing whether scheduled and real-time syncs run on their own.
    • Granted scopes — the OAuth permissions you approved, listed as chips. If none were reported you see No scopes reported.

  3. Check the Monthly API usage row on the same card to see how much of your Airtable API allowance this connection has spent. The chip reads used, cap, and percent (for example, 4,200 / 5,000 (84%)), backed by a colored bar:

    • A primary (blue) bar means usage is comfortably within budget.
    • A warning (amber) bar appears as you approach the cap, alongside the message "Approaching your monthly Airtable API limit — consider reducing sync frequency or disabling real-time."
    • An error (red) bar appears at the cap, alongside "Monthly Airtable API limit reached — outbound sync is paused until it resets." Outbound writes stay paused until the monthly reset.

    If no usage snapshot is available for the connection, the whole usage row and its alerts are hidden — that is expected, not an error. The cap is also tracked as the Airtable Monthly API Cap Reached sync-health alert, covered in Reliability, limits, and sync-health alerts.

  4. Scan the four quick-stat cards below the Connection card for a one-glance summary:

    • Datasets synced — the number of dataset mappings configured.
    • Enabled — how many of those mappings are switched on.
    • With errors — how many mappings ended their last run with errors; the number turns red when it is above zero.
    • Last sync — reads Synced with the most recent sync timestamp beneath it, or Never if nothing has synced yet.

    While the numbers load, each card shows a skeleton placeholder in place of its value.

  5. Open the Activity tab to watch work that is running right now. When any Airtable job is in progress, an In progress card lists each one with a live progress ring, the job name, and its current status. You see this card for the three long-running Airtable operations — dataset syncs, Ops Hub base provisioning, and applying inbound changes. When nothing is running, the card is hidden.

  6. Read the Recent syncs table beneath it to see the outcome of each mapping's most recent run. Each row shows:

    • Dataset — the dataset label, with its direction (outbound or inbound) and schedule (Every 15 minutes, Hourly, Daily, or Manual only) underneath — the same values you set in the mapping editor, described in Sync-mapping settings reference.
    • Last synced — the timestamp of the last run, or Never.
    • Result — a concise summary such as 12 created · 3 updated · 1 failed, built from the run's created, updated, deleted, skipped, and failed counts. Zero-valued counters are dropped, so a clean run with nothing to do shows a dash.
    • Errors — a green OK chip when the run had no errors, or a red chip with the error count.

  7. To read the actual failure messages, hover the red error-count chip. Its tooltip lists the result summary followed by each recorded per-record error message. If a run recorded a count but no message detail, the tooltip reads No error detail recorded.

    While the table loads it shows skeleton rows. If you have not added any mappings yet, it shows the empty message "No syncs yet. Add a dataset mapping and run a sync to see activity here."

How this stays current​

These panels refresh on their own when a job finishes — you do not need to reload the page. The Result and Errors columns always reflect a mapping's most recent run, so an older failed run is replaced the moment a newer clean run completes.

For the mechanics behind this — the tracked background jobs that drive the auto-reload, and how a fresh clean run auto-resolves the Airtable Sync Failed alert — see How Airtable sync works and Reliability, limits, and sync-health alerts.

Next steps​

Last verified: