---
title: "Task Status"
method: GET
path: "/api/v2/tasks/{task_id}"
tags: ["tasks"]
---

# Task Status

`GET /api/v2/tasks/{task_id}`

## Request

- The document declares no server URL.
- Auth: none declared

One accepted request's outcome.

``404`` once it has aged out of ``memorize.async_queue.row_retention_hours``
(or never existed).

## Path parameters

- `task_id` string, required

## Response `200`

Successful Response

- SuccessEnvelopeTaskItem
  - `request_id` string, required
  - `data` TaskItem, required: ``GET /tasks/{task_id}`` -- one accepted request, in the Cloud's shape. ``id`` is the request id of the accepting call. Cloud also emits ``pending`` (accepted, boundary not run yet); this build never does, so a client written for Cloud sees a subset of the statuses it already handles.
    - `id` string, required
    - `status` 'queued' | 'processing' | 'success' | 'failed', required
    - `task_type` 'memory_add' | 'memory_flush', required
    - `error` string, nullable
    - `error_code` string, nullable
    - `created_at` string, date-time, required
    - `finished_at` string, date-time, nullable

## Other responses

- `422`: Validation Error

## Changes

- **2026-10-20** `6beb324a48dd`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/evermind-ai/apis/everos/changes/api/v2/tasks/:task_id/get.md)

---

[API](https://skmtc.dev/evermind-ai/apis/everos.md) - [All operations](https://skmtc.dev/evermind-ai/apis/everos/llms.txt) - [OpenAPI document](https://skmtc.dev/evermind-ai/apis/everos/revisions/8f6c6973c7e6?raw)