study_case_submit

Purpose and availability

Build only: queue one EXACT named case/version, returning its durable job ID. Poll study_status, then inspect study_results. No implicit latest version.

Before invocation

Inspect the current definition and exact version/project binding before invoking. Required fields, enums, bounds and consent fields below are authoritative. Omit no required input and do not invent unavailable values.

Exact input schema

{
  "additionalProperties": false,
  "properties": {
    "case_id": {
      "maxLength": 256,
      "minLength": 1,
      "type": "string"
    },
    "key": {
      "maxLength": 256,
      "minLength": 1,
      "type": "string"
    },
    "version": {
      "pattern": "^[a-f0-9]{64}$",
      "type": "string"
    }
  },
  "required": [
    "case_id",
    "version"
  ],
  "type": "object"
}

Results, errors and safety

Inspect the structured result and retained IDs/artifacts. Errors, unsupported profiles, missing data and cancellation remain explicit. A successful call grants no human engineering approval. Do not retry inference automatically. See Workflows, History and Project tools.