Policy violation
For the complete documentation index, see llms.txt. For a full content snapshot, see llms-full.txt. Append .md to any kestra.io/docs/* URL for plain Markdown.

A governance policy blocks the flow from running, so no execution is created.

  • HTTP status — 403 Forbidden
  • type — https://kestra.io/docs/api-reference/problems/policy-violation

When you get it

  • An execution is requested for a flow that the policies applying to it block.

The policy chain is resolved again at execution time, because a policy can postdate the flow. A flow that was accepted when it was saved can therefore still be blocked here.

Example response

A response reporting this problem:

{
  "type": "https://kestra.io/docs/api-reference/problems/policy-violation",
  "title": "Policy violation",
  "status": 403,
  "detail": "Execution blocked by governance policy: task type 'io.kestra.plugin.scripts.shell.Commands' is forbidden [policy=no-shell-tasks, task=run-script]",
  "instance": "/api/v1/main/executions/company.team/my-flow"
}

The detail names each blocking rule, the policy it came from, and the task it was raised on.

How to handle it

This is a 403 rather than a 409 by design: a 409 would suggest transient state the caller can retry past, and a policy denial is not one. Either the flow changes, or the policy does. See Policies.

For the members every problem document carries, see Problem Details.

Was this page helpful?