Review Playbook runs

Every Playbook run records its inputs, steps, decisions, outputs, warnings, and issues. Use this record to verify a result, understand an exception, and improve the Playbook.

Review results and outputs

When a run finishes, V7 Go collects output steps in one overview. Use this overview to find the final reports, files, structured records, and integration results.

Runs can be queued, running, waiting for input, complete, or in error. A run that waits for input may need a connection or a human approval before it can continue.

Trace claims with citations

Citations connect a claim to the source that supports it. They are available only when the Playbook has a resolvable source and the step produces useful evidence. A claim from pasted text or an unsupported source may not have a citation.

Some workspaces show citations in HTML outputs as underlined claims. Selecting a claim opens its source and hovering shows the supporting quote. Citation display depends on workspace availability.

Understand confidence

Confidence estimates how completely the result meets the Playbook's explicit requirements. The product may show this score as a percentage. It is separate from the run status.

A run can have high confidence after a difficulty. For example, it may report trouble finding a file, recover, and complete all required work.

Warnings and issues

Warnings identify a problem in the Playbook definition, such as an incomplete path or a missing connection between steps. They help you correct the process before it runs.

Issues record operational friction during or after a run. A run can finish successfully and still report an issue, such as a missing integration, confusing instruction, or extra work that the process did not expect.

Use warnings and issues as evidence. They can show that you need to improve instructions, an input form, a resource, an integration, or a human review point.

Next steps

• Playbook outputs
• Improve a Playbook