You Edited the PAC File. Did the Browser Fetch It Again?
Saving a proxy script on its server does not establish that the browser replaced its cached configuration. Check retrieval before debugging the new rule.
You change the PAC file from proxy A to proxy B, save it, and reload a website. The website still sees proxy A. Before changing the rule again, check whether the browser even obtained the new script.
A page reload and a PAC download are different operations. The client may retain a script independently of the page being viewed. An already established connection adds another reason that the next visible activity may not demonstrate a fresh routing decision.
Look for a PAC request
Use the configuration server's access log and the client's available network diagnostics. Identify the exact PAC URL, the response, and the version of the script delivered. A file edited in one directory can coexist with a different file served by the active web host.
Chromium documents its own PAC caching and refetch behavior. Other clients have their own rules. Avoid turning an old “restart the browser” anecdote into a universal refresh interval.
Make the comparison meaningful
If a controlled fresh browser session is appropriate, use the supported configuration mechanism and confirm the retrieval rather than relying only on a settings screen. Be aware that closing a window does not always terminate every browser process.
Once the new script is known to be loaded, inspect its result for the destination. Only then investigate connection reuse or the proxy service's exit address. Those later stages cannot explain a PAC edit the client never received.