You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/toml_schema.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -169,6 +169,7 @@ Runs one of three judge-backed modes: `capability`, `escalation`, or `custom`.
169
169
|---|:---:|---|---|
170
170
|`mode`| No |`capability`| Classifier behavior. Set it explicitly for new configurations. |
171
171
|`classifier_target`| Yes | — | Target the judge is called through. Not a routing destination. |
172
+
|`target_failover`| No |`true`| When false, a failed selected completion target returns its error instead of trying another route target. |
172
173
|`max_output_tokens`| No |`4096`| Maximum completion tokens for the judge verdict. Must be at least `1`. |
173
174
|`response_format_type`| No |`json_schema`| Structured-output mode for capability and escalation judges. Use `json_object` when the provider does not support JSON Schema; Switchyard adds the schema to the prompt and validates the verdict locally. Custom mode always uses its configured JSON Schema. |
0 commit comments