Runs

Unarchive Runs

Restores up to 250 archived runs in one fail-soft, non-transactional request. Each run is processed independently and successful items emit the same per-run unarchive events as POST /api/v1/runs/{id}/unarchive. A valid batch returns 200 even when some items fail; inspect results and summary for per-run outcomes. Invalid request bodies are rejected before mutating any run.

post/api/v1/runs/unarchive

Request body

run_idsstring[] required

Run IDs to process, in result order.

Example request

{
  "run_ids": [
    "01HZX6M29F1CD5YYMHT1F5D7WQ"
  ]
}

Response

Batch processed

Example response

{
  "results": [
    {
      "run": {
        "repository": {
          "name": "fabro-sh/fabro",
          "origin_url": "https://github.com/fabro-sh/fabro.git"
        },
        "lifecycle": {
          "error": {
            "message": "Stage 'apply-changes' exceeded maximum retries."
          }
        },
        "timing": {
          "wall_time_ms": 420000,
          "inference_time_ms": 120000,
          "tool_time_ms": 60000,
          "active_time_ms": 180000
        },
        "diff": {
          "files_changed": 42,
          "additions": 567,
          "deletions": 234
        },
        "pull_request": {
          "owner": "fabro-sh",
          "repo": "fabro",
          "number": 123,
          "html_url": "https://github.com/fabro-sh/fabro/pull/123"
        },
        "current_question": {
          "text": "Accept or push for another round?"
        }
      },
      "error": {
        "status": "404",
        "title": "Not Found",
        "detail": "Run not found.",
        "code": "access_token_expired"
      }
    }
  ]
}

Changes

Changed in 13 of the 139 revisions of this API.11320

Aug 31, 202618883371dc6f23See the full diff
- ▲
  removed the required property ///////////// from the response with the status
  response-required-property-removed
- ▲
  removed the required property ///////////// from the response with the status
  response-required-property-removed
- ○
  added the optional property ///////////// to the response with the status
  response-optional-property-added
- ○
  added the optional property ///////////// to the response with the status
  response-optional-property-added
- ○
  added the required property ///////////// to the response with the status
  response-required-property-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 31, 20262ca60fd095f91See the full diff
- ○
  added the optional property //////// to the response with the status
  response-optional-property-added
Jul 28, 2026ef906071a8e412See the full diff
- ●
  added the new publish_failed enum value to the ///////// response property for the response status
  response-property-enum-value-added
- ○
  the response property //////// became required for the status
  response-property-became-required
- ○
  the response property //////// became required for the status
  response-property-became-required
Jul 28, 20267fe7b675579921See the full diff
- ▲
  the response property //////// became optional for the status
  response-property-became-optional
- ▲
  the response property //////// became optional for the status
  response-property-became-optional
- ○
  removed the publish_failed enum value from the ///////// response property for the response status
  response-property-enum-value-removed
This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jul 28, 20264f9aedeb721112See the full diff
- ●
  added the new publish_failed enum value to the ///////// response property for the response status
  response-property-enum-value-added
- ○
  the response property //////// became required for the status
  response-property-became-required
- ○
  the response property //////// became required for the status
  response-property-became-required
Jul 28, 2026d043ecc9a6522See the full diff
- ▲
  the response property //////// became optional for the status
  response-property-became-optional
- ▲
  the response property //////// became optional for the status
  response-property-became-optional
This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jul 28, 2026fa4de608a93c2See the full diff
- ○
  the response property //////// became required for the status
  response-property-became-required
- ○
  the response property //////// became required for the status
  response-property-became-required
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jul 27, 202644617fd2c7221See the full diff
- ○
  removed the publish_failed enum value from the ///////// response property for the response status
  response-property-enum-value-removed
Jul 27, 2026ad4eeab2bd6f1See the full diff
- ●
  added the new publish_failed enum value to the ///////// response property for the response status
  response-property-enum-value-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jun 13, 2026de85d055604012See the full diff
- ▲
  added to the /// response property oneOf list for the response status
  response-property-one-of-added
- ○
  added discriminator to /// response property for the response status
  response-property-discriminator-added
- ○
  removed subschema #2 from the /// response property oneOf list for the response status
  response-property-one-of-removed
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history (13 revisions)