Skip to main content

Human Review

On hearing “review”, you may think of watching the agent's behavior and stopping it when something looks wrong. A review step is not that kind of mechanism.

This page explains what a review step decides. Where to put one and who to make the reviewer are in the Review Guide.

A review step decides whether to move the case on​

A review step belongs to workflows. It cannot be placed in a cycle. Build a task that needs a person's judgment as a workflow.

What a review step decides is whether that case may move on to the next step. The reviewer looks at the settings and artifacts of the version under review and chooses to proceed, send back, or reject.

It is not a mechanism that stops an agent's execution partway. It never interrupts while an agent is running. Prevent operations you do not want through how the agent is built and through the limits on outbound traffic, not through review (Execution Rules and Network Access Guide).

Even if you name several reviewers, the first one to answer settles it. It does not wait for everyone to agree.

There are two review methods​

There are two review methods.

Wait for the reviewer's decision does not move on until a person decides. In the Marketplace edition, a review is not decided automatically even after its deadline. After the deadline it notifies the reviewer and keeps waiting.

External wait is a method where the case moves on by the state of an external service rather than by a person. The external condition available now is “merge of a GitLab MR”. When it is met, the case moves on automatically. A person cannot advance it. They can only send it back or reject it.

Moving on by an external condition is not an approval​

When a case moves on automatically because an external condition was met, no reviewer answered. The record also shows that it moved on by “the external condition being met”, not by a person's decision.

Mixing these up leads to misreading the track record. When you read review figures as a record of people's responses, tell apart what moved on by an external condition (Records and Metrics).

A review is pinned to a version​

A review request is made on the “version being reviewed”. If, while it awaits review, the owner makes the case's settings a new version, the content under review is replaced with the new version. An artifact switches to the new version when the version passed to the next step was the one that was edited (otherwise, choose the version to pass again in the case settings). The reviewer looks at the replaced content and decides again.