MGS3037: a job record field fails its shape

magus job fork, magus job apply and magus\job.put refused a job record because one of its fields cannot be read as declared:

[MGS3037] timeout "soon" is not a positive duration: name one such as 30m or 2h,
  or leave it out

Nothing was written to the job store. Every problem in the record is reported at once, each naming its field (write_paths[2], waivers[0].reason), so one edit can clear them all.

What fires it

• id, parent or a depends_on entry that is not a lease id: letters, digits and -_./: only, at most 128 characters.
• A state outside the job states, a timeout that is not a positive Go duration, or a negative max_attempts.
• A relative checkout. A fork names the checkout it makes by an absolute path.
• A write, deny or read path that begins with ~, is absolute, or climbs out of the workspace with ... The guard matches paths relative to the workspace root, so such a path bounds nothing.
• A blank breaks entry.
• A field sent under both its current and its renamed spelling, or check beside a rendered validation line.
• enter beside any other declared field. A record carrying enter enters a job and declares nothing.
• An unknown member.
• A waiver on a code that cannot be waived, or with no subject or no reason. Only MGS3043, MGS3044 and MGS3045 can be waived.

What to do

Edit each field the problem names, using the fix it prints, and send the record again. magus job fork --schema prints the shape every field must take.

See also

• Leases: what each field of a job record means.
• MGS3038: a goal no evidence could grade.