An execution whose report was ignored

When a session ends, it leaves a report of its work in a file called report.json. HarmFlow reads the execution's outcome and the result of each work item from that report. When the report cannot be used, HarmFlow ignores it, and the work items' results it held are lost.

When a report is ignored

HarmFlow ignores a report that:

• Is not valid JSON.
• Does not follow its schema, such as a field of the wrong type.
• Follows its schema but cannot be read into HarmFlow's own records, such as a number too large for its field.

Why it reads Needs attention

An execution whose report was ignored ends with the status Needs attention, not Completed, even when the session itself finished. Without its report, HarmFlow cannot tell what the session did with its work items, so the execution asks you to look at it.

Reading the reason and the warning

The execution shows the reason its report was ignored, and a warning on it says the same. The reason says which of the three cases above applied. For a report that does not follow its schema, both the reason and the warning name the field the validator found at fault, and what is wrong with it. For example, a report that gives the first work item's pull request as a plain link names the field /workItems/0/pullRequest: workItems is the list of work items, 0 the first of them, and pullRequest its field.

The field and what is wrong with it tell you where the report and its schema disagree.

What happens to the work items

Each work item the session selected counts one failure, toward the task's limit of retries, since its result was lost with the report.