The Commit Bar#

The Commit Bar floats over the bottom of the page whenever something is pending. Editors do not change the router: their Save, Add and Delete buttons add to the pending changes, and this bar is where those changes are reviewed and applied. It offers four actions: Review changes, Apply with auto-revert, Apply changes and Discard. It is the only part of the web interface that applies anything.

What it shows without being asked#

A dot, and a count: 3 pending changes. The count is the number of changes as the list below states them, one per thing changed, not the number of configuration operations underneath.
The most recent change as a sentence, with (+2 more) after it when there are others. Narrow screens leave it out.
Any error from the last attempt to add, remove, discard or apply changes, as a button that dismisses it. The router's reason is kept and the command text around it is left out.

Nothing in the pending changes has reached the router. With nothing pending and no error to report, the bar is not shown; it appears with the first change an editor adds.

Reviewing the pending changes#

Review changes opens the list, grouped by the area each change belongs to (System, Certificates, Firewall and so on). Each change is one sentence, marked + when something is added, ~ when it is changed and − when it is removed, with its particulars on a second line:

	Change	Particulars
+	Add time server time.cloudflare.com	With NTS
~	Change the host name to edge-1
+	Add router account alice	Full name “Alice Example”, password set
−	Remove scheduled task “backup”

Each line has a Remove button, which takes that change back out of the pending changes. A line covers everything done to one object, so removing it removes all of it.

The sentences never contain a secret. A password, a pre-shared key, an SNMP community or a private key is described as having been set or changed, never shown, whatever the reader's role.

How it marks a change that could cut you off#

Some changes can end your own connection to the router. The bar marks them: the dot turns amber, the affected lines are shown in the warning colour, Apply changes is styled as a destructive action, and the list opens with These changes could cut off your connection to the router. Apply with auto-revert undoes them if you lose access. Nothing is disabled or hidden.

A change is marked when it touches:

What	Why it is on the list
Firewall rules	A rule that drops your session drops your session.
NAT	Address translation decides whether the reply reaches you.
The SSH service, the HTTPS service or the router's API service	The management services themselves.
An interface's addresses, its DHCP client options, or turning it off (VLANs included)	Readdressing the router is how a session ends.
Anything on an interface the router uses as an uplink, or on the parent of one	Turning off or changing the parent interface takes its VLANs with it.
The router's own DNS servers	Your own tools may depend on the names the router resolves.
A default route, IPv4 or IPv6, and default route distances	They decide which way packets leave, including yours.
Failover, load balancing, policy routing and routing tables	Every multi-WAN mechanism decides which way packets leave.
High availability	Virtual addresses move.
Certificates	The certificate the web interface serves can vanish.
Router accounts	An account change can lock you out of the console and SSH.

Apps are never marked: an app's containers and their network are not the router's own.

The uplinks are read from the router's own routing, so the rule follows whichever interfaces this router leaves through, not a fixed interface name. Read the mark as a prompt, not as a verdict: any change can cut you off, and Apply with auto-revert is offered whether or not anything is marked.

What the two apply buttons do#

Apply with auto-revert (2 min) applies the pending changes and starts a timer on the router. Unless Keep changes is pressed before it runs out, the router restarts with its saved configuration. The number is the auto-revert window, set by an admin under Admin → Agent settings (1 to 60 minutes, 2 by default). The browser sends the window with the request, and only an admin's browser can read the setting, so below admin the window is 2 minutes whatever the setting says. What happens next is on Apply with auto-revert.

Apply changes applies them with no timer. The change is permanent as soon as the router accepts it.

Both take the same road through the agent:

If there is nothing to apply, including when another session emptied the pending changes a moment ago, it says so and sends nothing.
Every pending change goes to the router in one request, which the router applies as one unit.
If the router refuses, the refusal is recorded in the audit log with the router's reason, the bar shows that reason, and the pending changes stay as they were, so the change can be corrected and applied again.
If it succeeds, the audit log records who applied what, the pending changes are cleared, and the router archives the result as a new revision.

Applied changes take effect at once. The router starts with them after a restart only once the configuration is saved: Save configuration on the System page.

Discard#

Discard throws the pending changes away. It asks first, with Discard 3 changes?, and disarms itself after five seconds if that is not pressed. The pending changes are shared by every session on the router, so a discard can remove work another person prepared. It is recorded in the audit log with what was discarded.

What it will not do#

It will not apply by itself. No page, editor or background task in the web interface applies changes. The reconcile loop can, but only when it has been deliberately started to do so; see Desired state.
It will not apply part of a set. Either every pending change applies or none does.
It will not hide a refusal. A change the router refuses comes back with the router's own reason.
It will not offer its buttons to a role that cannot use them. A viewer sees Your role cannot apply changes in their place. An approver can review and apply changes others have prepared, but cannot remove a change from the list or discard them. The agent enforces the same rules on its routes; see Read plane, write plane, admin plane.

In Advanced mode#

With Advanced mode on (Account → Preferences), the list shows the configuration operations themselves: one set or delete per line, marked + or −, each with a × that removes that single operation, followed by a Commands block holding the whole set as text. The count in the bar is then the number of operations, and the most recent command replaces the most recent sentence. Errors are shown in full. See Advanced mode and the router's commands.