USusenash
Optimization Run Re-solve

Read the re-solve of an optimization run that dropped orders

Changed on

Returns the result of solving a run that newly dropped orders, and the previous run, again with their stored inputs. reading says whether the change between the runs caused the drop. status is pending while the solves run, and not_requested when none was queued or the result has expired. Both are a 200.

get/v1/activities/{id}/unassigned-resolve

Request

Path parameters

idstring required

Activity id

Example:act_123

Response

OK

schema_version'unassigned-resolve/v1'
status'pending' | 'done' | 'failed' | 'no_new_drops' | 'no_previous_run' | 'input_missing' | 'unsupported_solver' | 'not_comparable' | 'not_requested' required
reading'not_the_change' | 'change_caused_drop' | 'partly_reproduced' | 'change_causes_other_drops' | 'inconsistent' | 'not_reproduced'

What the fresh solves show. Declaration order is the order in which the rules apply.

recorded_new_dropsstring[]
previous_activity_idstring nullable
queued_atstring date-time nullable
solved_atstring date-time nullable
errorstring nullable

Changes