Stack Exchange recently added 3 new restrictions to "prevent unauthorized access to the network". Global Flag Summary was 1 of 5 automatic processes added to a community made list of process that would potentially be broken by the new restrictions. Stack Exchange said that "we do not believe our efforts will impact a significant number of community tools", but Global Flag Summary appears to have been, err... impacted. Only 57 out of the 244 it was looking for (for this purpose a per-site meta and the main site are different sites) were actually reached, making the script nearly useless. Note that, at the end, it started to actually to change from 404 to rate-limited. Note that I tried about 20 of the links that were "404"s and they all worked fine. In addition to the above, it also logged me out network-wide and gave me a Cloudfare thing when I tried to access SE again. Here is a screenshot of a small section of the errors:

Could this please be fixed?

When running the Global Flag Summary userscript, 57 out of the 244 sites it calls to were successful, and the rest produced error status codes. Most produced 404 status codes, but towards the end of running the script, the response code changed from 404 to rate-limited. When I manually tried to access about 20 of the links that were listed as "404"s, they all worked fine. 

In addition to the above, running this script also logged me out network-wide and gave me a Cloudfare challenge when I tried to access SE again. 

Here is a screenshot of a small section of the errors:

Stack Exchange recently added 3 new rate limits to "prevent unauthorized access to the network," and these changes may be the cause of the new 404/rate-limiting errors.

Could this please be fixed?

Stack Exchange recently added 3 new restrictions to "prevent unauthorized access to the network". Global Flag Summary was 1 of 5 automatic processes added to a community made list of process that would potentially be broken by the new restrictions. Stack Exchange said that "we do not believe our efforts will impact a significant number of community tools", but Global Flag Summary appears to have been, err... impacted. Only 57 out of the 244 it was looking for (for this purpose a per-site meta and the main site are different sites) were actually reached, making the script nearly useless. Note that, at the end, it started to actually to change from 404 to rate-limited. Note that I tried about 20 of the links that were "404"s and they all worked fine. In addition to the above, it also logged me out network-wide and gave me a Cloudfare thing when I tried to access SE again. Here is a screenshot of a small section of the errors:

Could this please be fixed?

Stack Exchange recently added 3 new restrictions to "prevent unauthorized access to the network". Global Flag Summary was 1 of 5 automatic processes added to a community made list of process that would potentially be broken by the new restrictions. Stack Exchange said that "we do not believe our efforts will impact a significant number of community tools", but Global Flag Summary appears to have been, err... impacted. Only 57 out of the 244 it was looking for (for this purpose a per-site meta and the main site are different sites) were actually reached, making the script nearly useless. Note that, at the end, it started to actually to change from 404 to rate-limited. Note that I tried about 20 of the links that were "404"s and they all worked fine. In addition to the above, it also logged me out network-wide and gave me a Cloudfare thing when I tried to access SE again. Here is a screenshot of a small section of the errors:

Could this please be fixed?