---
title: Status and error reference
description: Choose the next step based on the failure type instead of retrying blindly.
lastVerified: 2026-09-23
---

# 7.2 Status and error reference

A status describes how work is progressing; an error explains why it did not continue. Find the relevant execution record before deciding whether to retry.

## Common work states

- Waiting or queued: execution has not started. Check the assigned colleague and prerequisites.
- Running: the model or tools are still working. Check the latest activity.
- Needs your attention: something needs more information, a decision, or permission.
- Completed: execution has ended. Check the result against the acceptance criteria.
- Failed or stopped: inspect the cause, any external effects that already occurred, and the available recovery options.

The exact UI labels can differ by object. An automation's enabled state and the state of an individual task run are separate fields.

## Recognizable error categories

| Error | Meaning and next step |
| --- | --- |
| `teloa/invalid-input` | Invalid input format or fields. Check the indicated location and pinned versions. |
| `teloa/forbidden` | The operation is not allowed. Check identity, scope, and permissions; do not bypass them. |
| `teloa/storage-corrupt` | Stored data does not match the expected identity or digest. Preserve evidence, then check the source. |
| `reference/not-found` | The reference is not available. List readable references first. |
| `reference/version-conflict` | The reference version has changed. List it again and verify the new version; do not automatically replace old evidence. |
| `reference/source-unavailable` | The file, encoding, size, or source prevents reading. |

This table covers common categories, not every error code. The current contracts define the complete error objects. Include the redacted message, version, and triggering action in an issue report.