Jobs are long-running tasks that are executed asynchronously. Jobs are identified by their job ID, in the form of job-1569583053767
, which is returned when starting a job. Subsequent job updates are published over the websockets API.
There are two events that are published regarding jobs:
job-data-{jobId}
- status update on the job, e.g. progress when training a neural network. Provides a single argument: { data: 'string with status' }
.
job-finished-{jobId}
- indicator that the job finished. Provides a single argument: { success: true }
which indicates whether the job was executed successfully.
You can also cancel a job through the websocket by sending a job-cancel
event. Pass in one parameter (the job ID).
Get the logs for the multi-impulse migration job in this project. This is a separate route so public projects can access it. If no multi-impulse migration jobs are present, an error will be thrown.
Project ID
Maximum number of results
Log level (error, warn, info, debug)
error
, warn
, info
, debug
Get the logs for a job.
Project ID
Job ID
Maximum number of results
Log level (error, warn, info, debug)
error
, warn
, info
, debug
Download the logs for a job (as a text file).
Project ID
Job ID
Maximum number of results
Log level (error, warn, info, debug)
error
, warn
, info
, debug
Export the training pipeline of a Keras block. Updates are streamed over the websocket API.
Project ID
Learn Block ID, use the impulse functions to retrieve the ID