The "Reload policies" button at chrome://policy makes Chrome fetch the policy protobufs from DMServer, but not the actual contents of the component policies (that is, policies for extensions).

This means that if the first fetch of the component policies in a single session failed for some reason (like a network error or a server error), then the user won't have any ability to force them being reloaded ahead of the scheduled retry time. The automatic retry interval varies depending on the error type, but it can be up to 12 hours.

We should probably fix this by ensuring that the "Reload policies" button is also applied to the component policies.


And that's all besides the probable need of revisiting the automatic retry logic: the configured intervals seem to be excessively long, and they don't take the network state into account (which can lead to problems once the delay grows exponentially to a big value).


Technically, ignoring of the manual request happens due to the logic in ExternalPolicyDataUpdater::FetchExternalData(), which returns immediately if there is already a job for the given tuple (component_key, URL, hash max_size) - and it counts the jobs delayed due to errors too.