Check Result Object
Response schema for check results
When you fetch the results of a Job using the /getJobById
or /getJobByCaseId
endpoint, the response will contain a check result object with metadata about the check execution and a check-specific payloads for each check that was run. You can find the results of a specific check by filtering the command_name
in the response.
The unique identifier of the agent.
The unique identifier for this instance of the agent.
The unique identifier of the command.
The name of the command.
A description of what the command does.
The unique identifier for this instance of the command.
The identifier of the data loader used, if any.
The identifier of the job this check result belongs to.
The timestamp when the check result was created.
The timestamp when the check result was last updated.
The timestamp when the data loader started, if applicable.
The timestamp when the data loader finished, if applicable.
The timestamp when the check started.
The timestamp when the check finished.
The type of result, typically “CommandResult”.
The current status of the check result (e.g., “pending”, “complete”, “failed”).
The step number in the workflow, if applicable.
The input data used for the check.
The verification data used for the check. Input data will be compared against this data.
Whether the check passed.
A human-readable summary of the check result.
A detailed explanation of what was checked and how the result was determined.
Check-specific result data. The structure of this object varies depending on the type of check that was run. See the individual check result documentation for details:
An object containing any alerts or warnings generated during the check.
A recommended action based on the check result.
Any instructions related to the check.
Any follow-up actions that should be taken.
Any evidence collected during the check.
Any error that occurred during the check.
An array of status messages emitted during the execution of the check.