Sync Status

The sync status indicates whether the edge gateway is running the latest configuration published from the cloud. You can view it in the Config Sync card on the deployment's Configuration page.

Status states

The card can also show In Sync (changes pending) — the gateway is running the latest published configuration, but there are unpublished changes waiting in the Pending Changes card.

Status transitions

Shadow created → Pending
                    ↓
          Config published → Pending
                    ↓
     Runtime starts applying → Applying
                    ↓
         ┌─── Success ───┐─── Failure ───┐
         ↓                               ↓
      In Sync                          Error
         ↓                               ↓
  New config published → Pending   New config published → Pending

Detailed transitions

Pending → Applying: The Edge Runtime detects pending changes during its 30-second poll cycle and marks the shadow as applying before it applies the configuration.

Applying → In Sync: The runtime successfully applies the connector and binding changes to its in-process protocol drivers and reports the applied config version to the cloud.

Applying → Error: The application fails on the edge and the failure is recorded on the shadow.

Applying → Pending: The runtime successfully applies the configuration, but by the time it reports back, a newer desired version has already been published. The shadow remains pending because there are still unapplied changes.

In Sync → Pending: A new configuration is published (either manually or via auto-publish), incrementing the desired config version above the reported version.

Error → Pending: A new configuration is published, resetting the sync status to pending. The runtime will attempt the new configuration on its next poll cycle.

Config sync card

The deployment's Configuration page displays a Config Sync card with:

Version tracking

• Desired version — the config version published from the cloud
• Applied version — the last config version successfully applied on the edge

When the desired and applied versions match, the deployment is In Sync.

Timestamps

• Published — when the last configuration was published from the cloud
• Applied — when the edge gateway last applied a configuration

Actions

• Preview Changes — inspect exactly what will be sent to the gateway before publishing
• Publish Config — push the current configuration to the gateway
• A refresh button to re-fetch the latest state

Error display

When the sync status is Error, the card displays a Sync Error block with the failure details.

Monitoring sync progress

A typical sync cycle takes less than a minute:

1. Configuration is published — status changes to Pending
2. Within 30 seconds, the Edge Runtime polls and detects the change
3. Status changes to Applying
4. The runtime applies the configuration to its drivers (usually a few seconds)
5. Status changes to In Sync

If the status remains Pending or Applying for more than a few minutes, check that the gateway is Online and review the runtime logs on the edge server. See Troubleshooting for guidance.