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 Status card on the deployment detail page.

Status states

Status transitions

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

Detailed transitions

Pending → Applying: The config agent detects pending changes during its 30-second poll cycle and marks the shadow as applying before it downloads the configuration bundle.

Applying → In Sync: The agent successfully applies all device profiles and device configurations to the local Fleetera Edge instance and reports the applied config version to the cloud.

Applying → Error: The agent encounters an error during application (for example, an invalid device profile or an unreachable edge service) and reports the failure with error details.

Applying → Pending: The agent successfully applies the configuration, but by the time it reports back, a newer desired version has already been published. The shadow remains in pending state 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 agent will attempt to apply the new configuration on its next poll cycle.

Config sync status card

The deployment detail page displays a config sync status card with the following information:

Version tracking

• Desired version — the config version published from the cloud
• Applied version — the last config version successfully applied on the edge
• Version diff — the number of versions between desired and applied

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

Timestamps

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

Device services summary

A collapsible section lists the edge device services included in the configuration:

• Each service shows the number of profiles and devices
• Expanding a service reveals the individual device names
• This helps you verify that the correct connectors and bindings are included

Error display

When the sync status is Error, the card displays the error details:

• Error message describing what went wrong
• Error code (DOWNLOAD_ERROR or APPLY_ERROR)
• The resource that caused the error (for example, a profile name)
• The timestamp of the error

Monitoring sync progress

The config sync status card auto-refreshes every 30 seconds when the deployment is online. You can also manually refresh to check the latest state.

A typical sync cycle takes less than a minute:

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

If the status remains in Applying for more than a few minutes, check the config agent logs on the edge server for errors. See Troubleshooting for guidance.