Auto-Publish

Auto-publish controls whether configuration changes are pushed to edge gateways automatically or require manual action. Each deployment has its own auto-publish setting, so you can use different strategies for different gateways at the same site.

How auto-publish works

When auto-publish is enabled (the default), the platform automatically publishes a new configuration to the edge gateway whenever a relevant change occurs. You do not need to manually trigger a publish — the system handles it for you.

When auto-publish is disabled, the platform marks the deployment's shadow as having pending changes but does not publish. You must manually publish the configuration from the deployment detail page.

Triggers

The following actions trigger auto-publish for all deployments at the affected site:

Action	Description
Binding created	A new variable binding is created for an asset at the site
Binding updated	An existing binding's address or parameters are modified
Binding deleted	A variable binding is removed
Connector attached	A connector is attached to an asset at the site
Connector detached	A connector is detached from an asset

When any of these actions occur, the platform evaluates each deployment at the site:

Auto-publish enabled — the configuration is published immediately
Auto-publish disabled — the sync status is set to Pending and a notification is created

Notifications for manual publish

When auto-publish is disabled and a configuration change occurs, the platform creates a notification to alert you that manual action is required. The notification includes:

The deployment name
The pending config version number
A message indicating that manual publish is required

You can view pending notifications from the Notifications section of the platform.

Configuring auto-publish

To toggle auto-publish for a deployment:

Navigate to the site and open the Edge Gateway tab
Select the deployment
In the Configuration section, use the Auto-publish config toggle switch

The change takes effect immediately. Turning auto-publish on does not retroactively publish any pending changes — you must manually publish if there are changes waiting.

When to disable auto-publish

Auto-publish is convenient for most deployments, but you may want to disable it in these situations:

Production gateways — where you want to review and approve configuration changes before they reach the edge
Shared sites — where multiple team members may be editing bindings and you want to batch changes into a single publish
Testing — where you want to make several binding changes before pushing them to the gateway

Even with auto-publish disabled, the platform still generates the configuration and detects changes. The only difference is that the configuration is not pushed to the edge until you manually publish it.