Skip to main content

Answer an agent the guard keeps blocking

A rule in Gate or Lock mode blocks an agent's change that breaks it. When the same rule blocks the same agent too many times in a row (Blocks before asking on the Settings tab, 5 unless someone changed it), the agent stops and asks one question on its task. The question is headed Guard and reads "Architectural Guard keeps blocking '' on . How should I proceed?". The task waits until someone answers.

What you can pick depends on the rule's mode:

OptionOffered forWhat it does
Grant waiver (7 days)Gate rulesWaives this rule on the whole project for 7 days. The agent retries its change.
Stop taskEvery ruleEnds the task: the agent fails it, naming the rule.
Keep tryingLock rulesThe agent keeps changing the code until it complies. A Lock rule never allows a waiver.

Before you start: the Guard runs only where your organization has the Architectural Guard. Compliance itself is part of some plans only.

Who can do this: anyone who can answer the task's questions can pick Stop task or Keep trying. Grant waiver (7 days) also needs the permission to edit compliance on the task's project. Without it the answer is refused and the question stays open for someone who has it.

  1. Find the question. In the sidebar, select Compliance, then the Guard activity tab, and set Decision to Escalated. Each row is a time an agent reached the limit and asked. The task also shows a ? and the state Asking on the board.
  2. Select the row's number under Task. The task opens on its Q&A tab, on the question headed Guard. Hover an option to read what it does.
  3. Decide whether the rule is right here. Back on Guard activity, set Rule to the same rule to see how often it blocks, or open the rule's page to read its fix guidance and every repository it fails on, as in See where a rule fails. Often the agent is wrong and the rule is right: then stop the task, or for a Lock rule have it keep trying.
  4. Pick one option. Picking it on the last open question sends the answer; on an earlier one, finish the others first, as in Answer a task's question.
  5. Watch the task carry on. The task shows Delivering, then:
    • after Grant waiver (7 days), the agent retries the change, and Guard activity gains a Waived row for the rule;
    • after Stop task, the task ends failed, with the rule named in its reason;
    • after Keep trying, the agent works on, and its count of blocks starts again from zero.
  6. After a grant, check the waiver. Open the repository's compliance page, or the rule's page under Active waivers. The waiver names you as its owner, expires 7 days from the grant, and reads Granted from task #, linking the task. To end it early, select ⋯ on its row, then Revoke, as in Waive a compliance gap.

A grant can still be turned down after you send it: when the rule's policy allows no waivers, or only waivers shorter than 7 days, or the rule no longer exists. The agent is told why and either changes its code or stops the task; no waiver is filed.

If many escalations name the same rule, change the rule rather than answering each one: clearer fix guidance, or Advise mode while you work it out. See Change how strictly a rule is enforced.