OutputError
Job billed to user: yes

Input and Output Errors

An InputError or OutputError may occur for the following reasons:
    Input/Output specification mismatch: these errors only occur if an executable has specified an input or output spec
      the value provided for a particular input/output field does not match the class specified (e.g., "int", "record", "array:file"); see Job Input and Output for details on the expected syntax
      the value provided for a particular input/output field does not match the type specification (e.g. "Reads")
      a referenced data object cannot be found
    The following errors are thrown only as OutputErrors because the analogous input errors are thrown at the time of the API call that creates the origin or master job:
      a required output field is missing
      an extra output field has been provided
    Object state error: the job is an origin or master job, and it has a data object that would be cloned for output that is still in the open state, but it and all of its descendant jobs have all finished running and so there is no thread of execution that can close the object
    Syntax errors
    Resolution errors
      a job-based object reference refers to a field that is not present in the output of the specified job
      a job-based object reference refers to a job that has failed and therefore cannot be resolved
      a job-based object reference refers to a job that the job that has finished running does not have permission to describe
Last modified 2yr ago
Export as PDF
Copy link