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

# AutomationTestRun

> What one test run of a workspace did. Nothing it did was stored or performed.

**Required scopes:** [`automations_read`](/docs/api-reference/v3/reference/scopes#scope-automations_read)

**failure**

Why the run failed; null unless `status` is FAILED.

**fields**

**message** `String!` *required*

The error the run stopped on.

**stepId** `String`

The step that failed, or null for the run as a whole.

**logs**

What each Function step's code logged, by step id.

**records**

The scenario's records after the run, with the steps' writes applied, by record id.

**rejection** `String`

Why the automation declined to run; null unless `status` is REJECTED.

**status** *required*

Where the run ended. WAITING when it waits on something the scenario never answers; see `waitingOn`.

**steps** *required*

The steps the run executed, in order, with their inputs, outputs and effects, as in `AutomationRun.steps`.

**fields**

**effects** *required*

Side effects the step performed, each with its result.

**finishedAt**

When the step finished; null while it runs or waits.

**inputs**

The step's evaluated config.

**kind** `String!` *required*

The step's kind.

**note** `String`

A note the step left, such as why it was skipped.

**outcome** `String`

completed, disabled, failed or cancelled; null while running.

**output**

What the step produced, as later steps read it.

**port** `String`

The output port the run left the step by.

**startedAt** *required*

When the step started.

**stepId** `String!` *required*

The step's id in the automation's script.

**unanswered** `[String!]!` *required*

Lookups the scenario didn't answer, as `resolver.field`; the run used each field's fallback. Answer them in the scenario's `records` or `resolvers`.

**waitingOn** `String`

What a WAITING run waits for that the scenario never answered, such as an event.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.