How changes reach the edge
A saved change represents your desired configuration. It does not establish that every serving location uses that configuration.
Saved and active state
An API mutation writes desired state first. Configuration publication and application happen separately. During convergence, requests can encounter different applied revisions. A successful response, a resource ready timestamp or an active certificate status is not a complete end-to-end traffic check.
The configuration polling default is 10 seconds, with a server-provided delay. This is not an end-to-end rollout guarantee. Certificate issuance and cache publication have additional stages.
Check a change
Follow traffic verification: read the saved resource, inspect its readiness fields and request the site behavior you changed. For TLS, check the presented certificate. For L4, use your application protocol.
If readback and observed behavior differ, ask your NetActuate account manager to confirm the applied configuration. No fixed maximum propagation time is established by the available sources.