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

# Executions

> Execution statuses, artifacts, and suggested workflows.

## Execution statuses

Each workflow run moves through these statuses:

| Status      | Meaning                                   |
| ----------- | ----------------------------------------- |
| `pending`   | Queued, waiting to start.                 |
| `running`   | The agent is performing the test.         |
| `success`   | The test passed.                          |
| `failure`   | The test failed.                          |
| `cancelled` | You cancelled the run before it finished. |

Deterministic failures trigger a [summarization](/workflow-lifecycle#summarization) step. Lark classifies the failure as a script issue (auto-repair) or a product regression (alert via Slack/Linear). AI-driven executions skip this step.

Check an execution's status in the [dashboard](https://dashboard.getlark.ai/workflows) or through the API:

```bash theme={null}
curl https://api.getlark.ai/workflows/wf_abc123/executions/exec_xyz789 \
  -H "X-API-Key: $GETLARK_API_KEY"
```

## Artifacts

Each execution can produce artifacts: files the agent captured or generated during the test. You can download them from the [dashboard](https://dashboard.getlark.ai/workflows) or through the API.

<img src="https://mintcdn.com/lark/dzcEV4wLHRMyRiPz/images/artifacts.png?fit=max&auto=format&n=dzcEV4wLHRMyRiPz&q=85&s=0cb6a0a0e935441081a52cd4a2b94cf4" alt="Screenshot showing the artifacts in the execution detail page in dashboard." style={{ borderRadius: '0.5rem', maxWidth: '400px', height: 'auto'}} width="2148" height="1208" data-path="images/artifacts.png" />

### Artifact types

| Type          | Description                                  |
| ------------- | -------------------------------------------- |
| `screenshot`  | A screenshot the agent took during the test. |
| `video`       | A recording of the full test session.        |
| `javascript`  | JavaScript code the agent executed.          |
| `python`      | Python code the agent executed.              |
| `shellscript` | Shell commands the agent ran.                |

### Accessing artifacts (API)

Artifacts appear in the execution response under the `artifacts` array. Each entry includes:

* `artifact_type` - One of the types above.
* `filename` - The file name.
* `presigned_url` - A download URL.
* `presigned_url_expires_at` - When the URL stops working.

```json theme={null}
{
  "artifacts": [
    {
      "artifact_type": "screenshot",
      "filename": "login-page.png",
      "presigned_url": "https://...",
      "presigned_url_expires_at": "2026-03-25T12:00:00Z"
    }
  ]
}
```