It's also working as intended [:)] There are scenarios that would cause your configuration to change that don't involve a second admin logging into the box and making changes.
Most commnly, DNS based hostnames get updated automatically, when needed. This would trigger that the configuration has been changed, and cause your webadmin session to need to re-sync. Dyndns type hosts would be the most prone to cause this type of event, since they typically have a very short ttl, and would be refreshed more often.
I don't definitely know whether the re-syncing is triggered by time, or is event driven, but when working with customers, (both the customer and I logged in simultaneously) I have seen webadmin re-cache objects shortly after the customer makes a change - suggesting it is event driven. My session was not idle for more than a few seconds. Normally, the caching is pretty quick, and not an annoyance. If you're on a slow link, and have a large config, it can take a bit more time.
100MB - Just short of a minute wait. No DynDNS in the production Astaro. Three DNS Host definitions and one DNS Group defintion. None of which has changed in months.
If it works as intended, then it wasn't working as intended prior to 7.400, and it wasn't working as intended in 7.450.
Cheers - Bob
Sophos UTM Community Moderator Sophos Certified Architect - UTM Sophos Certified Engineer - XG Gold Solution Partner since 2005
100MB - Just short of a minute wait. No DynDNS in the production Astaro. Three DNS Host definitions and one DNS Group defintion. None of which has changed in months.
If it works as intended, then it wasn't working as intended prior to 7.400, and it wasn't working as intended in 7.450.
Cheers - Bob
Sophos UTM Community Moderator Sophos Certified Architect - UTM Sophos Certified Engineer - XG Gold Solution Partner since 2005