Troubleshooting

​

Quick Triage Flow

​

Creation and Setup Issues

​

”Add Guardrail” button not visible

Likely cause: Missing required permission. Fix:

1. Verify your role has guardrail management permissions.
2. Refresh session and retry.

​

Provider list is empty or missing expected provider

Likely cause: Provider access not configured or unavailable. Fix:

1. Confirm provider credentials/licensing.
2. Validate provider availability in your environment.
3. Retry after configuration update.

​

Probe Selection Issues

​

Cannot find expected probe

Likely cause: Active filters/search narrowing results. Fix:

1. Clear search and status filters.
2. Switch to broader tags (for example, All).
3. Verify provider selection in the workflow.

​

Deployment Issues

​

Deployment remains pending

Likely cause: Incomplete target selection or backend processing delay. Fix:

1. Confirm project and endpoint are valid.
2. Re-open deployment details and check status transitions.
3. Retry deployment if no progress occurs.

​

Guardrail not applied to endpoint

Likely cause: Wrong deployment type or mapping mismatch. Fix:

1. Confirm you selected Add to Existing Deployment if needed.
2. Check deployment mapping in guardrail detail and project tabs.
3. Redeploy with corrected target.

​

Runtime Quality Issues

​

Too many false positives

Fix:

• Reduce severity slightly.
• Disable or refine over-sensitive rules.
• Validate changes in a limited rollout.

​

Unsafe content still passing

Fix:

• Increase severity for key probes.
• Add missing probes for uncovered categories.
• Ensure both input and output guard types are enabled.

​

Escalation Checklist

Before escalating, collect:

• Guardrail profile name and ID.
• Selected provider and probes.
• Deployment target and current status.
• Example prompts/responses showing the issue.
• Timestamp of the most recent failure.

​

Governance Policy Issues

​

Governance policy cannot be saved

Likely cause: Missing policy name, conflict strategy, or required rule details. Fix:

1. Add a policy name.
2. Select a conflict strategy.
3. Ensure each rule has at least one check or action pattern.
4. If using action patterns, add at least one pattern before saving.

​

Governance policy is not available for an agent

Likely cause: The policy has not been deployed to the same project as the agent. Fix:

1. Open the policy from the Governance Policy tab.
2. Deploy it to the project that contains the agent.
3. Reopen the agent version and refresh the Governance section.

​

Tool action was allowed or denied unexpectedly

Likely cause: A conflicting rule, broad filter, or priority setting took precedence. Fix:

1. Review the policy conflict strategy.
2. Check rule priority values.
3. Inspect Only when filters for overly broad or missing context.
4. Verify whether an allow, deny, notify, or escalate rule matched the same tool action.