Documentation
FAQ
FAQ / Gotchas
Why did this BLOCK?
BLOCK means ASG determined the action must not execute.
Common causes:
- a managed policy matched with severity
block - required context was missing for a
blockpolicy - global safety controls prevented execution
- usage limits were exceeded and ASG blocked by default
When you receive BLOCK, you must not execute.
Why can't I edit rules?
In Managed Safety Mode, the managed policy catalog is vendor-owned and read-only.
Why is WARN not PASS?
WARN means ASG requires explicit human approval before execution.
WARN is not a soft PASS. WARN is a distinct decision state.
Why did my workflow stop?
Workflows must stop when:
- ASG returns BLOCK
- ASG returns WARN and approval is not confirmed
- ASG cannot be reached or a decision cannot be obtained safely
Stopping is required to enforce fail-closed behavior.
Legal & Responsibility Notice
Summary
Informational only
Provided for general guidance. Not legal, compliance, security, or professional advice.
You control implementation
You are responsible for policies, prompts, integrations, workflows, and regulatory requirements.
Liability limitation
To the maximum extent permitted by law, the company disclaims liability for losses arising from use of this documentation or implementations based on it.