> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jaantonio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace

> How to read statuses, notes, and classifications when a document stops.

The invoice workspace is where you follow stamping day to day. Three signals matter:

1. **Status** — the label on the document right now
2. **Note** — observed values and what disagreed
3. **Classification ID** — the precise reason Lambda paused

## How to read a stopped document

1. Note the workspace label — [Statuses](/stamping/statuses).
2. Open the document note for observed values and the classification ID.
3. Match the ID to [Failures](/stamping/failures) or [System errors](/stamping/system-errors).

**Failed** can mean either a document/provider problem or a system/support problem. The note and classification ID distinguish them. Both appear under the same workspace label so you always open the note first.

## Explore

<CardGroup cols={1}>
  <Card title="Statuses" icon="list-check" href="/stamping/statuses">
    Learn what each workspace label means.
  </Card>

  <Card title="Failures" icon="triangle-exclamation" href="/stamping/failures">
    See what Lambda catches — document and provider stops.
  </Card>

  <Card title="System errors" icon="screwdriver-wrench" href="/stamping/system-errors">
    See configuration, recovery, and support stops — including what Lambda fixes itself.
  </Card>
</CardGroup>

When Lambda can safely continue stuck work, or when a deliberate correction is needed, continue with [Recovery](/stamping/retry/overview).
