Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Cancel a running job.
Organization ID
Job ID
If set to 'true', we won't wait for the job cluster to cancel the job, and will mark the job as finished.
OK
Whether the operation succeeded
Optional error description (set if 'success' was false)
Get all jobs for this organization
Organization ID
Start date
End date
Maximum number of results
Offset in results, can be used in conjunction with LimitResultsParameter to implement paging.
Whether to exclude pipeline / transformation jobs
Whether to exclude jobs with a parent ID (so jobs started as part of another job)
Job key to filter on
Job category to filter on
OK
Whether the operation succeeded
Optional error description (set if 'success' was false)
Active jobs
Job id, use this to refer back to the job. The web socket API also uses this ID.
External job identifier, this can be used to categorize jobs, and recover job status. E.g. set this to 'keras-192' for a Keras learning block with ID 192. When a user refreshes the page you can check whether a job is active for this ID and re-attach.
When the job was created.
When the job was started.
When the job was finished.
Whether the job finished successfully.
The IDs of users who should be notified when a job is finished.
Additional metadata associated with this job.
Job duration time in seconds from start to finished, measured by k8s job watcher.
Some job categories keep a counter on the job number, e.g. in synthetic data, so we know what the 1st, 2nd etc. job was in the UI.
Get the logs for a job.
Organization ID
Job ID
Maximum number of results
Log level (error, warn, info, debug)
OK
Whether the operation succeeded
Optional error description (set if 'success' was false)
Total number of logs (only the last 1000 lines are returned)
Get the status for a job.
Organization ID
Job ID
OK
Whether the operation succeeded
Optional error description (set if 'success' was false)
Job id, use this to refer back to the job. The web socket API also uses this ID.
External job identifier, this can be used to categorize jobs, and recover job status. E.g. set this to 'keras-192' for a Keras learning block with ID 192. When a user refreshes the page you can check whether a job is active for this ID and re-attach.
When the job was created.
When the job was started.
When the job was finished.
Whether the job finished successfully.
The IDs of users who should be notified when a job is finished.
Additional metadata associated with this job.
Job duration time in seconds from start to finished, measured by k8s job watcher.
Some job categories keep a counter on the job number, e.g. in synthetic data, so we know what the 1st, 2nd etc. job was in the UI.
Get all active jobs for this organization
Organization ID
Whether to exclude jobs with a parent ID (so jobs started as part of another job)
OK
Whether the operation succeeded
Optional error description (set if 'success' was false)
Active jobs
Job id, use this to refer back to the job. The web socket API also uses this ID.
External job identifier, this can be used to categorize jobs, and recover job status. E.g. set this to 'keras-192' for a Keras learning block with ID 192. When a user refreshes the page you can check whether a job is active for this ID and re-attach.
When the job was created.
When the job was started.
When the job was finished.
Whether the job finished successfully.
The IDs of users who should be notified when a job is finished.
Additional metadata associated with this job.
Job duration time in seconds from start to finished, measured by k8s job watcher.
Some job categories keep a counter on the job number, e.g. in synthetic data, so we know what the 1st, 2nd etc. job was in the UI.
Get all finished jobs for this organization
Organization ID
Start date
End date
Maximum number of results
Offset in results, can be used in conjunction with LimitResultsParameter to implement paging.
Whether to exclude jobs with a parent ID (so jobs started as part of another job)
OK
Whether the operation succeeded
Optional error description (set if 'success' was false)
Active jobs
Job id, use this to refer back to the job. The web socket API also uses this ID.
External job identifier, this can be used to categorize jobs, and recover job status. E.g. set this to 'keras-192' for a Keras learning block with ID 192. When a user refreshes the page you can check whether a job is active for this ID and re-attach.
When the job was created.
When the job was started.
When the job was finished.
Whether the job finished successfully.
The IDs of users who should be notified when a job is finished.
Additional metadata associated with this job.
Job duration time in seconds from start to finished, measured by k8s job watcher.
Some job categories keep a counter on the job number, e.g. in synthetic data, so we know what the 1st, 2nd etc. job was in the UI.
Download the logs for a job (as a text file).
Organization ID
Job ID
Maximum number of results
Log level (error, warn, info, debug)
OK
Get a token to authenticate with the web socket interface.
Organization ID
OK
Whether the operation succeeded
Optional error description (set if 'success' was false)