Auto-Publish

Auto-publish controls whether routine 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

Every unpublished change is classified by impact (see Publishing Config): routine (binding-level changes), deferred (connection settings), and structural (changes to what the gateway runs).

When auto-publish is enabled (the default):

• Routine changes — binding creations, updates, and deletions — are published automatically. Publishes are debounced over a short window (about 30 seconds), so a batch of edits results in a single publish rather than one per change.
• Deferred and structural changes are never auto-published. They accumulate in the deployment's Pending Changes card until you publish them manually.

When auto-publish is disabled, no change is published automatically. The deployment's sync status is set to Pending, and every change waits in the Pending Changes card for a manual publish.

Triggers

The following actions produce changes for the deployments at the affected site:

Configuring auto-publish

To toggle auto-publish for a deployment:

1. Open the deployment and go to its Configuration page
2. In the Configuration card, use the Auto-publish config toggle

The change takes effect immediately. Turning auto-publish on does not retroactively publish pending changes — use Publish Now in the Pending Changes card if changes are 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 every configuration change before it reaches 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