Skip to main content
invalid_decision_questions means OpenType refused the question set of a decision run. Read this page when a decision run is refused with this code and you need to know which question, dependency or setting to change.

What happened

Route: POST /v1/runs with "kind": "decision". The questions, their dependencies, or the draws and think_tokens settings break one of the bounds below. The run was refused before it existed. Nothing was stored and nothing was charged. Every message starts with the decision questions are not acceptable: and ends with one of these reasons. The limits in the right-hand column are not part of the message text.

Questions and answers

Dependencies and conditions

Settings and size

Two related refusals use other codes. capability_hint problems are reported as invalid_verdict_schema, even on a decision run. A missing questions field, or a question_order that does not name exactly the keys of questions, is invalid_body.

How to fix

  1. Find the reason after the prefix in the tables above.
  2. Check every depends_on and ask_if against the ids in questions.
  3. For ask_if, use answer names, not indexes: yes or no for a noul question, the option name for choice, the level name for score.
  4. Split a set that is over 64 questions or 32 KiB into several runs.
  5. Send the corrected request. It was refused before a run existed, so you may keep the same Idempotency-Key.
Some problems are not caught here. Whether each answer label is a single token, and whether the set fits the answer template, are checked only when the run executes. A failure there ends the run with decision_unavailable. Keep option and level names short, simple words.

Example

A valid set with a condition: bucket is asked only when urgent is answered yes.