You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[docs-scanner] Unclear policy change timing in organization policies overview #26555
The "When policy changes reach developers" section creates confusion about timing by stating:
Policy changes reach developer machines within 5 minutes. When a synced change takes effect also depends on the policy type.
This phrasing suggests there are two separate delays: (1) a 5-minute sync delay, and (2) an additional type-specific delay after syncing. However, the individual policy pages all describe immediate effect after the sync completes:
network.md: "Once a policy change has synced to the developer's machine, it applies immediately to subsequent requests."
filesystem.md: "Once a policy change has synced to the developer's machine, it applies the next time a sandbox starts."
mcp.md: "Once a policy change has synced to the developer's machine, use-time rules apply to subsequent governed MCP requests."
Why this matters
Readers trying to understand when their policy changes will take effect are left uncertain whether there's a 5-minute delay plus additional waiting, or just the 5-minute sync delay. The phrase "When a synced change takes effect also depends on the policy type" implies additional delays beyond syncing, but the linked pages describe only the sync delay.
Suggested fix
Clarify that the 5-minute sync is the only delay, and that "when it takes effect" refers to the evaluation point (per-request vs. sandbox start), not an additional delay. For example:
Policy changes reach developer machines within 5 minutes. Once synced, when the change applies depends on the policy type: network and MCP policies apply to subsequent requests, while filesystem policies apply when a sandbox starts.
Or link directly to the specific sections without the ambiguous "also depends" phrasing:
Activity