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

# Get Cache Execution History

> Returns a paginated list of past sync executions for the specified cache, ordered from most recent to oldest. Each entry corresponds to one sync run (either incremental or full refresh) and includes its status, progress counters, error details (if failed), and lifecycle timestamps.

The `executionMode` field on each entry indicates whether that run was an incremental sync or a full refresh. Use the `limit` and `offset` query parameters to page through history; defaults are `limit=10` and `offset=0`.

Execution records have a retention window of 14 days after the cache or run is finalised, after which they are automatically removed.

<span style={{display: "flex", gap: "10px", flexDirection: "row", alignItems: "center"}}>
  <img src="https://cdn.peaka.com/badges/partner-api-key-badge.png" />

  <img src="https://cdn.peaka.com/badges/project-api-key-badge.png" />
</span>


## OpenAPI

````yaml get /data/projects/{projectId}/cache/{cacheId}/executionHistory
openapi: 3.0.1
info:
  title: Peaka Gateway API
  description: Peaka Gateway API Documentation
  version: '1.0'
servers:
  - url: https://partner.peaka.studio/api/v1
    description: Default Server URL (US Zone)
  - url: https://partner.eu.peaka.studio/api/v1
    description: EU Zone
security:
  - bearerAuth: []
paths:
  /data/projects/{projectId}/cache/{cacheId}/executionHistory:
    get:
      tags:
        - Data -- Cache
      summary: Get Cache Execution History
      description: >-
        Returns a paginated list of past sync executions for the specified
        cache, ordered from most recent to oldest. Each entry corresponds to one
        sync run (either incremental or full refresh) and includes its status,
        progress counters, error details (if failed), and lifecycle timestamps.


        The `executionMode` field on each entry indicates whether that run was
        an incremental sync or a full refresh. Use the `limit` and `offset`
        query parameters to page through history; defaults are `limit=10` and
        `offset=0`.


        Execution records have a retention window of 14 days after the cache or
        run is finalised, after which they are automatically removed.
      operationId: getCacheExecutionHistory
      parameters:
        - name: projectId
          in: path
          description: The unique identifier of the project that owns the cache
          required: true
          schema:
            type: string
          example: mtKDhe1U
        - name: cacheId
          in: path
          description: >-
            The unique identifier of the cache whose history is requested (UUID
            format)
          required: true
          schema:
            type: string
          example: 960bd651-7b3c-4511-9a88-18e14ac7742a
        - name: limit
          in: query
          description: Maximum number of execution records to return. Defaults to 10.
          required: false
          schema:
            type: integer
            format: int32
            default: 10
          example: 10
        - name: offset
          in: query
          description: >-
            Number of records to skip from the start of the result set, used for
            pagination. Defaults to 0.
          required: false
          schema:
            type: integer
            format: int32
            default: 0
          example: 0
      responses:
        '200':
          description: >-
            Execution history retrieved successfully. Returns an empty array if
            no executions exist for this cache.
          content:
            '*/*':
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/CacheExecutionInfo'
        '404':
          description: Cache not found for the given cacheId.
          content:
            '*/*':
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/CacheExecutionInfo'
components:
  schemas:
    CacheExecutionInfo:
      type: object
      properties:
        id:
          type: string
        executionMode:
          type: string
        status:
          type: string
        error:
          type: object
        progress:
          $ref: '#/components/schemas/CacheExecutionProgress'
        createdAt:
          type: string
          format: date-time
        updatedAt:
          type: string
          format: date-time
        finishedAt:
          type: string
          format: date-time
    CacheExecutionProgress:
      type: object
      properties:
        numberOfCachedRecords:
          type: integer
          format: int32
        numberOfInsertedRecords:
          type: integer
          format: int32
        numberOfUpdatedRecords:
          type: integer
          format: int32
        numberOfDeletedRecords:
          type: integer
          format: int32
        lastOffset:
          type: string
        lastCacheTxId:
          type: string
  securitySchemes:
    bearerAuth:
      type: http
      description: >-
        Use the Authorization header with the value 'Bearer <apiKey>' to
        authenticate. Partner API Keys have full access; Project API Keys are
        limited to their project scope. Learn more:
        https://docs.peaka.com/api-reference/authentication
      scheme: bearer
      bearerFormat: Api Key

````