Kicking off an API job with access to the workspace saved by another job?

Looking at, it looks like it should be possible to define a job that is not referenced in the workflow, and then use the API to kick it off. If part of that job’s steps is to attach_workspace, which workspace does it pick? Or is that not supported for jobs that are kicked off via API?

The second. It won’t have workspace to attach because it’s not part of a workflow.