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

# Retry Automation Execution

> Retries a failed execution. The failed execution's trigger payload is replayed as a new execution against the automation's current configuration, in a new workspace. The failed execution stays in the history.



## OpenAPI

````yaml /openapi.json post /v1/automations/{id}/executions/{executionId}/retry
openapi: 3.1.0
info:
  title: Replica API
  version: 2.0.0
  description: >-
    The Replica API allows you to programmatically manage cloud workspaces for
    AI agents. Use this API to manage environments (the org-scoped primitive
    workspaces are created from — including variables, files, skills, MCPs, warm
    hooks, start hooks, and warm pools), create and manage replicas, send
    messages, manage chats, stream events, read connected repositories and
    repository sets, and configure automations.
servers:
  - url: https://api.replicas.dev
    description: Production API
security:
  - apiKey: []
tags:
  - name: Workspace Identity
    description: >-
      Public OpenID Connect discovery and signing keys for verifying short-lived
      workspace identity tokens. Workspaces mint tokens for any audience they
      name; verifiers must require their own audience.
  - name: Environments
    description: >-
      Manage environments — the primitive that workspaces are created from.
      Variables, files, skills, MCPs, warm-hooks, and warm-pools are all scoped
      to an environment. Every organization has a singleton Global environment
      whose values apply to every workspace. Personal environments are scoped to
      the authenticated user and can be standalone or source-backed by a team
      environment.
  - name: Repository
    description: >-
      Read repositories and repository sets connected to your organization.
      Repositories are the underlying GitHub-connection layer; bind them to an
      environment to use them in workspaces.
  - name: Replica
    description: >-
      Manage replicas (workspaces) for AI agents. Workspace creation with `POST
      /v1/replica` accepts API keys and workspace engine-secret authentication.
      Other Replica operations also accept logged-in user JWTs from first-party
      clients.
  - name: Slack
    description: Attach Slack threads to Replicas workspaces
  - name: Automation
    description: >-
      Create and manage automations that trigger replicas on a schedule or in
      response to events
  - name: Media
    description: >-
      Read workspace media and obtain short-lived download or inline preview
      URLs
paths:
  /v1/automations/{id}/executions/{executionId}/retry:
    post:
      tags:
        - Automation
      summary: Retry Automation Execution
      description: >-
        Retries a failed execution. The failed execution's trigger payload is
        replayed as a new execution against the automation's current
        configuration, in a new workspace. The failed execution stays in the
        history.
      operationId: retryAutomationExecution
      parameters:
        - name: id
          in: path
          description: The unique identifier of the automation
          required: true
          schema:
            type: string
            format: uuid
        - name: executionId
          in: path
          description: The unique identifier of the failed execution
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: Retry started as a new execution
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TriggerAutomationResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '409':
          description: >-
            The execution has not failed, or another run is still reporting the
            same GitHub checks
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '429':
          description: The automation or organization is over its hourly execution limit
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          $ref: '#/components/responses/InternalServerError'
components:
  schemas:
    TriggerAutomationResponse:
      type: object
      description: Response after triggering an automation
      properties:
        execution_id:
          type: string
          format: uuid
          description: Unique identifier for the execution
        workspace_id:
          type:
            - string
            - 'null'
          format: uuid
          description: The workspace created for this execution
      required:
        - execution_id
        - workspace_id
    Error:
      type: object
      properties:
        error:
          type: string
          description: Error message
        details:
          type:
            - string
            - 'null'
          description: Additional error details
        code:
          type: string
          description: Machine-readable error code when available
      required:
        - error
  responses:
    Unauthorized:
      description: Unauthorized - Invalid or missing API key
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Forbidden:
      description: Forbidden - The authenticated account cannot access this resource
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    NotFound:
      description: Resource not found
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    InternalServerError:
      description: Internal server error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    apiKey:
      type: http
      scheme: bearer
      description: >-
        API key authentication. Obtain your API key from the Replicas dashboard
        under Organization → Settings → API Keys.

````