IOionworks
Pipeline

Multistart progress for a Data Fit element

Changed on

Multistart roll-up plus convergence traces, keyed by element.

This is the one resource a running Data Fit is polled through. The UI never enumerates the child jobs itself: a 100-start fit used to cost a request per child (and again on every window focus), which is what tripped the per-IP edge rate limit for offices behind one address. Traces are keyed by multistart index, so child job ids never reach the browser.

get/pipelines/elements/{element_id}/progress

Request

  • Base URL
    https://api.ionworks.com
  • URL
    https://api.ionworks.com/pipelines/elements/{element_id}/progress
  • Auth
    none declared

Path parameters

element_idstring uuid required

Query parameters

traces'best' | 'all'

Which convergence traces to include: the best multistart only (cheap enough to poll), or every multistart (one storage read per child; fetch once, on request).

Response

Successful Response

element_idstring required
status'pending' | 'running' | 'completed' | 'failed' | 'skipped' | 'canceled' required
best_indexinteger nullable
traces_completeboolean

Changes