> ## Documentation Index > Fetch the complete documentation index at: https://qovery-gdubroeucq-qov-2345.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # List agentic workflow runs > Returns the runs recorded for this agentic workflow, newest first: sorted by created_at descending, then by id descending. Runs are added as they are triggered, so a run added between two requests shifts the runs after it towards later pages. agenticWorkflowId is matched against source_workflow_id, the workflow a run was requested for. A CLONE_ENVIRONMENT run is listed under that workflow, not under the clone that executed it. There is no lineage resolution either, so a clone's own ID returns no runs at all. Only runs that were launched appear here. A trigger that failed before launching, such as one turned away by the rate limiter, leaves no run. Runs that predate this endpoint are not backfilled. ## OpenAPI ````yaml /api-reference/openapi.yaml get /agenticWorkflow/{agenticWorkflowId}/runHistory openapi: 3.0.0 info: version: 1.0.4 title: Qovery API description: > - Qovery is the fastest way to deploy your full-stack apps on any Cloud provider. - ℹ️ The API is stable and still in development. contact: name: Qovery Product Team url: https://www.qovery.com email: support+api+documentation@qovery.com x-logo: url: https://console.qovery.com/assets/logos/logo-white.svg altText: Qovery servers: - url: https://api.qovery.com security: - bearerAuth: [] - ApiKeyAuth: [] tags: - name: Account - name: Account Info - name: IPs - name: Alert Receivers - name: Alert Rules - name: Admin - name: ArgoCD - name: Agentic Workflows - name: Application - name: Application Actions - name: Application Configuration - name: Application Database - name: Application Deployment Restriction - name: Application Deployment History - name: Application Environment Variable - name: Application Logs - name: Application Main Calls - name: Application Secret - name: Application Annotations Group - name: Applications - name: AutoscalingPolicy - name: Container - name: Container Actions - name: Container Configuration - name: Container Database - name: Container Deployment History - name: Container Environment Variable - name: Container Logs - name: Container Main Calls - name: Container Registry - name: Container Secret - name: Container Annotations Group - name: Containers - name: Deployment Stage Main Calls - name: Job - name: Job Actions - name: Job Configuration - name: Job Database - name: Job Deployment Restriction - name: Job Deployment History - name: Job Environment Variable - name: Job Logs - name: Job Main Calls - name: Job Registry - name: Job Secret - name: Job Annotations Group - name: Jobs - name: KedaTriggerAuthentication - name: Helm - name: Helm Actions - name: Helm Configuration - name: Helm Database - name: Helm Deployment Restriction - name: Helm Deployment History - name: Helm Logs - name: Helm Main Calls - name: Helm Repository - name: Helms - name: Backups - name: Billing - name: Blueprint Catalog - name: Cloud Provider - name: Cloud Provider Credentials - name: Clusters - name: Cluster Deployment History - name: Cluster Operator - name: Platform Configuration - name: Custom Domain - name: Container Custom Domain - name: LLM Providers - name: MCP Servers - name: Database - name: Database Actions - name: Database Application - name: Database Container - name: Database Deployment History - name: Database Main Calls - name: Database Annotations Group - name: Databases - name: Environment - name: Environment Actions - name: Environment Deployment History - name: Environment Deployment Rule - name: Environment Logs - name: Environment Main Calls - name: Environment Secret - name: Environment Variable - name: Environments - name: Git - name: Github App - name: Git repositories - name: Members - name: Organization - name: Organization Account Git Repositories - name: Organization Cluster Lock - name: Organization Main Calls - name: Organization Custom Role - name: Organization Event - name: Organization Api Token - name: Organization Policy Api Token - name: Organization Webhook - name: Organization Annotations Group - name: Organization Labels Group - name: Organization Enterprise Connection - name: Project - name: Project Deployment Rule - name: Project Environment Variable - name: Project Main Calls - name: Project Secret - name: Projects - name: Referral & Rewards - name: Secret Manager Access - name: Terraforms - name: Terraform Main Calls - name: Terraform Resources - name: Terraform Deployment History - name: Terraform Deployment Restriction - name: Container Registries - name: Helm Repositories - name: User Sign Up - name: Variable Main Calls - name: Helm Custom Domain - name: Lifecycle Template Main Calls - name: Blueprint Main Calls paths: /agenticWorkflow/{agenticWorkflowId}/runHistory: get: tags: - Agentic Workflows summary: List agentic workflow runs description: >- Returns the runs recorded for this agentic workflow, newest first: sorted by created_at descending, then by id descending. Runs are added as they are triggered, so a run added between two requests shifts the runs after it towards later pages. agenticWorkflowId is matched against source_workflow_id, the workflow a run was requested for. A CLONE_ENVIRONMENT run is listed under that workflow, not under the clone that executed it. There is no lineage resolution either, so a clone's own ID returns no runs at all. Only runs that were launched appear here. A trigger that failed before launching, such as one turned away by the rate limiter, leaves no run. Runs that predate this endpoint are not backfilled. operationId: listAgenticWorkflowRunHistory parameters: - $ref: '#/components/parameters/agenticWorkflowId' - in: query name: page description: >- Page number, starting at 1. Increment this value to retrieve subsequent pages of run history, keeping pageSize unchanged. required: false schema: type: integer default: 1 minimum: 1 - in: query name: pageSize description: >- The number of runs to return in the current page. Must be between 1 and 100. required: false schema: type: integer default: 20 minimum: 1 maximum: 100 responses: '200': description: List run history content: application/json: schema: $ref: '#/components/schemas/AgenticWorkflowRunPaginatedResponseList' '400': $ref: '#/components/responses/400' '401': $ref: '#/components/responses/401' '403': $ref: '#/components/responses/403' '404': $ref: '#/components/responses/404' components: parameters: agenticWorkflowId: name: agenticWorkflowId in: path required: true schema: type: string format: uuid schemas: AgenticWorkflowRunPaginatedResponseList: allOf: - $ref: '#/components/schemas/PaginationData' - type: object properties: results: type: array items: $ref: '#/components/schemas/AgenticWorkflowRun' PaginationData: type: object required: - page - page_size properties: page: type: number example: 1 page_size: type: number example: 20 AgenticWorkflowRun: type: object description: One recorded run of an agentic workflow. required: - id - source_workflow_id - trigger - prompt - payload - created_at - recorded_at - status - started_at - finished_at - duration_ms properties: id: type: string format: uuid description: Run ID. source_workflow_id: type: string format: uuid description: >- ID of the workflow the run was requested for. A CLONE_ENVIRONMENT run executes as a fresh clone carrying its own ID, which run history does not report, so this is never the ID of the workflow that actually executed. trigger: $ref: '#/components/schemas/AgenticWorkflowRunTrigger' prompt: type: string nullable: true description: >- Agent prompt captured when the run was requested. It is a snapshot, so later edits to the workflow do not change it. Null when the workflow had no prompt. payload: type: string nullable: true description: >- Body of the event that triggered the run, as it was received: the webhook request body for a WEBHOOK run, empty for a SCHEDULE or MANUAL run. Request headers are never stored. The value is unredacted and supplied by the caller of the webhook, so treat it as untrusted text. Null when the run has no stored payload. created_at: type: string format: date-time description: Time the run was requested. recorded_at: type: string format: date-time nullable: true description: >- Time the run was registered in run history, shortly after it was requested. This is not a lifecycle start time: nothing reports when the agent itself started, so this value must not be used to measure a run. Null when it is unknown. status: $ref: '#/components/schemas/AgenticWorkflowRunStatus' started_at: type: string format: date-time nullable: true description: >- Time the run entered RUNNING. Separate from recorded_at. Null until that transition is observed, and null for a run that reached a terminal status without it being observed. finished_at: type: string format: date-time nullable: true description: Time the run reached a terminal status. Null until then. duration_ms: type: integer format: int64 nullable: true description: >- finished_at minus started_at, in milliseconds. Derived, not stored. Null unless both timestamps are set. AgenticWorkflowRunTrigger: type: string description: >- What triggered the run. MANUAL is a run started through the deploy endpoint, SCHEDULE a run started by the workflow's cron schedule, WEBHOOK a run started by its webhook. enum: - MANUAL - SCHEDULE - WEBHOOK AgenticWorkflowRunStatus: type: string description: >- Status of a run. COMPLETED, FAILED and CANCELLED are terminal and never change afterwards. enum: - QUEUED - RUNNING - COMPLETED - FAILED - CANCELLED responses: '400': description: Bad request '401': description: Access token is missing or invalid '403': description: Access forbidden '404': description: Resource not found securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- JWT tokens should be used with OIDC account (human to machine). JWT tokens used by the Qovery console to communicate with the API have a TTL. Curl Example ' curl https://console.qovery.com/organization -H "Authorization: Bearer $qovery_token" ' ApiKeyAuth: type: apiKey in: header name: Authorization description: >- Token API are generated by Qovery to manage machine to machine interaction and do not have a TTL. Curl Example ' curl https://console.qovery.com/organization -H "Authorization: Token $qovery_token" ' ````