Set the legs of a run
Replaces every leg of the run with the list you send, in order: the first you send is leg 1. At most 40. Each leg needs a start and an end; a driver must be a person in your organization. An empty list removes every leg. If anything is refused, the legs the run had are kept. Needs write on Animals. With scope=series the same chain is written to every run of the series, each leg’s times moved onto that run’s own date on the wall clock the rule records.
Authorizations
Query Parameters
Response
The run, with its new legs and problems.
Who is driving the run (Phase 436). On a run with legs this is whoever is in charge of the whole journey; each leg has its own driver. Empty text or null clears it. An address is only rewritten when its key is sent, so a patch about a date never clears one somebody verified.
Who to ring at the start (Phase 449b). An address gets a van to a car park; a name and a number get an animal out of it. Either half may be empty; both empty reads back as null. Only rewritten when the key is sent, so a patch about a date never clears a number somebody finally got hold of. An unknown field is refused rather than dropped.
Who to ring at the end (Phase 449b). An address gets a van to a car park; a name and a number get an animal out of it. Either half may be empty; both empty reads back as null. Only rewritten when the key is sent, so a patch about a date never clears a number somebody finally got hold of. An unknown field is refused rather than dropped.
Whether somebody decided this run goes (Phase 449d). Nothing here checks the weather - we do not know it - so this records that a person looked and what they said. Setting it stamps who and when; re-sending the same decision does not re-stamp it, and clearing it clears the stamp.
go, hold, null 
