Edge Agent synchronization lag during container state changes

When utilizing the Portainer Edge Agent to manage remote environments, the central instance relies on periodic polling to reflect the current status of hosted containers. However, there is uncertainty regarding the consistency of state updates when actions occur outside of the Portainer UI.

If a container is stopped, started, or restarted directly via the Docker CLI on the remote host, the Portainer dashboard does not always reflect these changes immediately. This delay appears to be tied to the internal polling interval of the agent, which impacts real-time monitoring of distributed edge nodes.

What parameters determine the frequency at which the Edge Agent reports environment state changes back to the primary server? Can this interval be adjusted via environment variables to reduce latency without significantly increasing outbound traffic overhead?