Troubleshoot Runtime Access Policies

Use this reference to diagnose common issues with Runtime Access Policy enforcement.
Symptom What to check
Policy doesn't apply to the expected agent Confirm the policy is active. Check the platform and agent scope. If the policy is intended to be global, confirm that both Platform and Agents are unselected. Check the enforcement schedule where applicable.
Approval requests aren't delivered Confirm that a Require Approval rule exists and that a valid HITL App is selected and configured.
File or Package validation isn't occurring Confirm Validate against threat feed is enabled for the applicable File or Package policy. This capability isn't available on other resource types.
File classification rule doesn't apply Confirm the DLP integration is configured and that the intended data classifications are selected in the File policy.
Version Control rule doesn't match Confirm the policy uses Version Control System rather than Terminal, and verify the configured repository URL and branch scope.
Policy schedule doesn't take effect Confirm selected days and time ranges include the current period and that the policy is active.