Sync Management

Sync management is a report of the background syncs between Full Fabric and connected apps. Staff use it to spot syncs that failed, read the error that caused them, and mark each failure as handled once it has been dealt with. It covers Canvas, Outlook and HubSpot.

Opening the Report

Open the Settings menu (the gear icon in the top bar) and choose Sync management. The page is titled Sync Management. Older links to the admin worker logs page redirect here.

Which Integrations Write to It

App What is recorded
Canvas Completed and failed sync runs
Outlook Completed and failed sync runs
HubSpot Failed syncs only; successful HubSpot syncs leave no entry

Salesforce syncs are not recorded here (see Salesforce).

The report keeps recent entries only: once its storage is full, the oldest entries are removed automatically.

What It Lists

Entries are shown newest first; click Last Update to reverse the order.

Column Shows
App Canvas, Outlook or HubSpot
Last Update When the entry was recorded
Status Completed, Failed or Handled
Error Message The error, for failed syncs
Trigger Type How the sync started (see below)
Sync Type What was synced
Entity The record synced, for example a person's name, a journey, or an email's recipients and subject
Synced Count Records synced; shown as processed / total when a run did not get through every record

Click a row that has an error message to open the Sync error window with the full text.

Trigger types

Trigger Type Meaning
Manual Started by a staff member, for example from a sync button
Scheduled Runs automatically on a recurring background schedule
Event Started by a change in Full Fabric data, such as a profile update, a journey change or a sent email. Every HubSpot entry is an Event

HubSpot sync types

Sync Type Meaning
User Profile, Create User Profile A profile synced to its HubSpot contact (Create is the first sync, which created the contact). Canvas uses the same types for Canvas users; the App column tells them apart
User Journey, Create User Journey A journey synced to its HubSpot deal (Create is the first sync, which created the deal)
Email A sent email recorded on HubSpot contacts
Profile Attachment A profile's files sent to its HubSpot contact
Application Attachment An application's files sent to its HubSpot deals

The Filter guide button at the top of the page describes every trigger type and every sync type, grouped by app, including those for Canvas and Outlook.

Filtering and Searching

Filter Options
State Completed, Failed (failed and not yet handled), Handled
App Canvas, Outlook, HubSpot
Sync Type One or more sync types
Trigger Type One or more of Manual, Scheduled, Event

The search box (Search by name, email or ID) accepts:

  • A profile ID: every entry about that person, including their journeys, their attachments and emails sent to them.
  • An email address: the same, for the profile that has this address. An address that matches no profile returns no entries.
  • Any other text: entries whose Entity contains the text, ignoring case.

Marking a Failure as Handled

Use Mark as handled once a failure has been dealt with, so the Failed filter only shows what still needs attention.

  1. Open the row's ⋯ menu, or click the row to open Sync error.
  2. Click Mark as handled. The status changes to Handled, and the Sync error window shows who handled it and when.
  3. To undo, use Unmark as handled; the entry goes back to Failed.

Only failed entries can be marked as handled. Marking an entry does not retry the sync or change anything else: fix the cause (for example the field mapping) and the record syncs again at its next change. If someone else changed the entry at the same time, the window says the status could not be updated and the report refreshes.

Permissions

Action Who can do it
Open the report and read errors Staff with Sync management (integrations.sync_management_access)
Mark or unmark entries as handled Staff with Sync management changes (integrations.sync_management_change), which includes Sync management

Without Sync management changes, the ⋯ menu and the handled buttons are not shown. These permissions are separate from Global integrations, so staff can review sync failures without being able to change integration settings. See Features & Permissions for how features are assigned to roles.