---
title: "Fv Run Redrive"
method: POST
path: "/v1/internal/fv-runs/{run_id}/redrive"
---

# Fv Run Redrive

`POST /v1/internal/fv-runs/{run_id}/redrive`

## Request

- Base URL: `https://api.graphify.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.graphify.com/v1/internal/fv-runs/{run_id}/redrive`
- Auth: none declared

Re-dispatch a run whose live SQS message died in the FV DLQ.

Called by the ``graphify-fv-redriver`` draining the FV dead-letter queue.
``attempt`` is the ``attempt`` the DLQ message carried, which anchors the
idempotency guard against re-delivery. The body's ``action`` (``redriven`` /
``dropped`` / ``deferred``) tells the drainer whether to delete or leave the DLQ
message. ``FvRunnerRequired`` (not the direct-session recorder the attempt
endpoints use) because redrive re-publishes through the transport, which is only
wired when FV is configured -- during a mid-flight disable this 503s and the
drainer leaves the message, which is the intended "retry when FV is back"
behaviour.

## Path parameters

- `run_id` string, uuid, required

## Query parameters

- `attempt` integer, required

## Response `202`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graphify/apis/graphify-control-plane.md) · [All operations](https://skmtc.dev/graphify/apis/graphify-control-plane/llms.txt) · [OpenAPI document](https://skmtc.dev/graphify/apis/graphify-control-plane/revisions/0e75c82b5ea8?raw)