Troubleshooting

Blocked by policy errors

Understanding 403 policy_violation responses from export, run, refine, and publish.

4 min read

When an action violates effective policy, APIs return 403 with payloads such as:

  • policy_violation
  • policyKey (e.g. disableJsonExport, disablePlaygroundForRoles)
  • Human-readable message

Common governance blocks in workflow automation:

  • PRODUCTION_APPROVAL_REQUIRED when lifecycle status is draft, in_review, or restricted
  • requireApprovalBeforePublish when approval is attempted before submit
  • requireScanBeforePublish when security scan gates are enabled

The UI component BlockedByPolicy surfaces these errors. Ask your admin which workspace role you have and whether org or workspace policy blocks the action.

Tip: If your n8n/Make run fails in production, retry with environment: "staging", then submit and approve the prompt/stack in review queue before promoting.

Related articles