Set when a blocked agent asks for help
When a rule in Gate or Lock mode blocks an agent's change, the agent reads the rule's fix guidance and tries another way. If the same rule keeps blocking it, the agent stops after a set number of blocks in a row and asks a question on its task, so a person can decide. Blocks before asking is that number. It is 5 until someone changes it, and it applies to every project in your organization.
Lower it when agents waste time circling the same rule; raise it when they usually find their own way around a block after a few tries.
Before you start: the setting shows only where your organization has the Architectural Guard. Compliance itself is part of some plans only.
Who can do this: changing it needs the permission to edit compliance. Without it, the tab shows the current value as text and says "Changing settings needs compliance edit."
-
In the sidebar, select Compliance, then the Settings tab.
-
Find the Architectural Guard section. Blocks before asking shows the current number.

-
Hover over the label to read what it counts: blocks in a row before the agent asks.
-
Type a whole number from 1 to 50. Anything else shows "Enter a whole number from 1 to 50." under the field, and Save stays greyed out.
-
Select Save. The button reads Saving… for a moment, then the field keeps the new number.
-
Later, select the Guard activity tab and set Decision to Escalated. Each row is a time an agent reached the limit and asked. Select its number under Task and answer the question, as in Answer a question.
If many rows are Escalated on the same rule, the number is rarely the problem: make the rule's fix guidance clearer, or set its mode to Advise while you do. See Change how strictly a rule is enforced.
Related
- How compliance works: how the Guard blocks a change and when an agent asks.
- Review what the guard blocked: list the Guard's decisions and follow one to its task and rule.
- Repository compliance: every field on the Settings tab.