policy: A policy refuses the action
A policy document governing this budget (its own, or a bound organisation or team policy) refuses the open, meter or reservation. The detail names the rule (kill_switch, empty, depth, category, payee, window, per_transaction, period, vendor_limit, velocity, policy_error) and the policy version. Nothing was allocated or billed.
What to do
- A policy governing this budget refuses the action (the detail names the rule and the policy version); dry-run it with POST /owner/v1/policies/dry-run.
On the wire
HTTP 409. What a refused meter or reservation receives depends on the request:
- With
Dynamo-Error-Detail: 1, or on a route added in owner-api 1.4.0 or later (for example a payment authorization), every client receives{"error": "halted", "reason": "policy", "streamId": "…", "detail": "…", "errorDetail": {…}}, whatever version it pins. - Without it, on the older routes (tick, meter, reserve and the plugin wire's meter), a client pinned at
Dynamo-Version1.8.0 or later receives{"error": "halted", "reason": "policy", "streamId": "…", "detail": "…"}. A client pinned before 1.8.0 receives the same body with its legacy reasoncap. On a single-tenant core a request that names no version is answered as pinned before 1.8.0 (cap); on the multi-tenant hosted tier it is served the account's default version, which is 1.8.0 for new accounts, so it receivespolicy.detailnames the rule and the policy version either way.
A stream open answers {"error": "mandate", "reason": "policy", "detail": "…"} (with errorDetail only when the request sends Dynamo-Error-Detail: 1). A child open on the plugin wire (POST /plugin/v1/streams/{id}/children) answers {"error": "child open refused (fail closed)", "reason": "policy"}.
See policies and all error codes.