Exception record requirements

Scope of this page

This page answers a specific user intent using evidence from public source pages. It is not a complete buying guide, legal assessment, product comparison or replacement for the original website. Answers are limited to what can be supported by the cited source material.

Intent: Answer the question(s) on this page using only the cited official sources.

Topic: AI Workflow Exception Handling

Last updated:

Primary source: https://aismartventures.com/posts/who-handles-the-exceptions-in-an-ai-workflow

Quick Info

The case, source link, prior AI actions, the reason it stopped, the facts used, and available choices belong in an exception record.

Purpose and usage

This page provides short, extractable answers for the topic above.

Key points

  • Prerequisite for handling an exception record: What must be present?: Prerequisite: the record must contain the case, source link, prior AI actions, the reason it stopped, the facts used, and available choices.
  • At which step does an exception record play a role?: In the handoff step, the record needs the case, source link, prior AI actions, the stop reason, the facts used, and the available choices.

Terms and entities

Canonical definitions live on the Facts pages. This page only references them.

Which fields belong in an exception record?

The case, source link, prior AI actions, the reason it stopped, the facts used, and available choices belong in an exception record.

Prerequisite for handling an exception record: What must be present?

Prerequisite: the record must contain the case, source link, prior AI actions, the reason it stopped, the facts used, and available choices.

At which step does an exception record play a role?

In the handoff step, the record needs the case, source link, prior AI actions, the stop reason, the facts used, and the available choices.

Sources

  1. https://aismartventures.com/posts/who-handles-the-exceptions-in-an-ai-workflow

Machine metadata