Fine-tuning job objects¶
The four control APIs return the same job DTO, with string code=OK, msg=OK, and data on success. Only fields actually returned by current HTTP are listed here; other persisted-model fields do not automatically become API capabilities.
Field |
Type |
Description |
|---|---|---|
|
string |
Stable job ID for subsequent queries, start, and cancellation. |
|
string |
Workspace owning the job. |
|
string |
Business idempotency identifier from the creation request. |
|
string |
Frozen base model identifier. |
|
string |
pending/running/succeeded/failed/cancelled。 |
|
array (strings) |
Frozen, sorted training run_id set. |
|
array (strings) |
Frozen, sorted validation run_id set. |
|
object |
Saved training configuration. Start may add run_traces; omitted without content. |
|
string |
Specified compute instance; omitted when empty. |
|
string |
Completed adapter URL; omitted when empty. Not an inference service URL. |
|
string |
Orchestration task association; omitted when empty. Temporary launching: values are not usable workflow task IDs. |
|
string |
Orchestration instance association; omitted when empty. Temporary launching: values are likewise not run IDs. |
|
string |
Job failure or cancellation code; omitted when empty. |
|
string |
Job error description; omitted when empty. |
|
string |
Control-plane start/claim time, not guaranteed to be GPU training start time; omitted when unset. |
|
string |
Time the job entered its terminal state; omitted when unset. |
|
string |
Job creation time. |
|
string |
Latest modification time. |
Times use UTC RFC3339, optionally with fractional seconds. Current creation requires both run_id sets to be nonempty. Examples show currently valid creation data.
The complete backend DTO has 18 fields, while dedicated Go/Python job types retain only nine: job_id, workspace_id, request_id, base_model, status, compute_resource_id, adapter_uri, error_code, and error_message. The other nine fields are unavailable through these dedicated return types.
Interpreting state¶
Status |
Current meaning |
Next step |
|---|---|---|
pending |
Saved; start claiming has not completed. |
Start as needed. A saved, unstarted result is not completed training. |
running |
The control plane claimed the job or entered running; preparation/dispatch may still be ongoing. |
Continue querying the job; this does not establish GPU activity. |
succeeded |
The current executor returned an acceptable result and saved adapter_uri. |
Confirm execution mode and actual adapter accessibility before a separate deployment process. |
failed |
Preparation, dispatch, training, artifact, or another stage failed. |
Read error_code/error_message and check recovery conditions. |
cancelled |
The control plane recorded cancellation as a terminal state. |
Stop polling. Confirm subprocess stopping and external resource cleanup through their respective protocols. |
succeeded, failed, and cancelled are terminal. GET returns no execution mode, metric list, log list, model backend ID, endpoint ID, or publication state. This DTO cannot establish model publication or complete preservation of all runtime diagnostics.