Get Validation
Path Parameters
Response
Successful Response
Schema for job information response
Possible types for a job
dummy, datafit, array_datafit, validation, simulate, evaluate_variables, optimize, ecm_fit, simple_pipeline Possible statuses for a job
pending, processing, waiting, completed, failed, canceled Whether the job has reached a terminal state and will not transition further.
Derived from :attr:JobStatus.TERMINAL_STATUSES, so adding a new
terminal status to the enum automatically updates the wire field —
clients that read is_terminal never need to know the status
taxonomy or be re-released when it changes.
Whether the job terminated unsuccessfully (failed or canceled, not completed).
Derived from :attr:is_terminal minus the success case, so any new
non-success terminal status added to :class:JobStatus is
automatically classified as a failure without touching this method.
Deep-link to this job's Anyscale console dashboard, or None.
Built server-side (mirroring the Sentry log_url pattern) from the
captured anyscale_job_id and the environment's console cloud/project
ids. Returns None when the job never ran on Anyscale (local/serve) or
the environment has no console ids configured, so the UI simply omits
the link in those cases.
Machine-readable error codes for jobs.
CONFIGURATION_ERROR, MODEL_ERROR, SOLVER_ERROR, EXECUTION_TIMEOUT, SUBMISSION_FAILED, INTERNAL_ERROR 1 - 2083Possible access levels for a job
project, organization