> ## Documentation Index > Fetch the complete documentation index at: https://docs.enginy.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get actions run status > Check the status of an actions run. `overallStatus` collapses every underlying process into one of PENDING/PROCESSING/QUEUED (in progress), COMPLETED/FAILED/CANCELLED (uniformly terminal), or PARTIAL (mixed terminal outcomes). `statusCounts` breaks progress down per record (contacts or companies × actions): pending, processing, and queued are in-flight; completed, failed, and cancelled are terminal outcomes; alreadyUpToDate counts records the worker skipped because they were already current; blocklisted counts completed records whose target is on the workspace blocklist (already excluded from `completed`). Use `lastUpdatedAt` to detect staleness — a run stuck at PROCESSING/QUEUED with an old `lastUpdatedAt` may indicate a worker backlog rather than active progress. > **Required scope:** `ACTIONS_READ` > > **Rate limit:** 100 requests per minute ## OpenAPI ````yaml https://openapi.enginy.ai/definitions.json get /v1/actions/{actionsId}/status openapi: 3.1.0 info: title: Enginy API version: 1.0.0 description: Public API for Enginy platform servers: - url: https://openapi.enginy.ai description: Configured server security: [] tags: - name: AI Variables description: >- Manage AI variables and discover the entity fields you can reference in prompts and entity requests. - name: Inbox description: >- Inbox endpoints for listing contact threads, reading thread messages, managing tags, and sending manual replies. - name: Workflows description: >- Build, validate, publish, run, and inspect advanced (graph) workflows, plus the block/condition catalog needed to author a workflow plan. paths: /v1/actions/{actionsId}/status: get: tags: - Actions summary: Get actions run status description: >- Check the status of an actions run. `overallStatus` collapses every underlying process into one of PENDING/PROCESSING/QUEUED (in progress), COMPLETED/FAILED/CANCELLED (uniformly terminal), or PARTIAL (mixed terminal outcomes). `statusCounts` breaks progress down per record (contacts or companies × actions): pending, processing, and queued are in-flight; completed, failed, and cancelled are terminal outcomes; alreadyUpToDate counts records the worker skipped because they were already current; blocklisted counts completed records whose target is on the workspace blocklist (already excluded from `completed`). Use `lastUpdatedAt` to detect staleness — a run stuck at PROCESSING/QUEUED with an old `lastUpdatedAt` may indicate a worker backlog rather than active progress. > **Required scope:** `ACTIONS_READ` > > **Rate limit:** 100 requests per minute parameters: - schema: type: string description: The actions ID returned from the run endpoint required: true description: The actions ID returned from the run endpoint name: actionsId in: path responses: '200': description: Actions group status retrieved successfully content: application/json: schema: type: object properties: status: type: string enum: - success message: type: string data: type: object properties: actionsId: type: number description: Unique identifier for the actions group entity: type: string enum: - CONTACT - COMPANY description: The type of entity overallStatus: type: string enum: - PENDING - PROCESSING - COMPLETED - FAILED - QUEUED - CANCELLED - PARTIAL description: >- Overall status of the actions group, collapsed across every underlying process: `QUEUED` (created, not yet picked up), `PENDING`/`PROCESSING` (in progress), `COMPLETED` (every record finished successfully), `FAILED` (every record failed), `CANCELLED` (every record was cancelled), or `PARTIAL` (a mix of completed and failed/cancelled records). Prefer `statusCounts` for the per-record breakdown behind this rollup. totalActions: type: number description: >- Total number of records this run is processing — sum of every bucket in `statusCounts`. Includes contacts/companies the worker decided not to re-process (`alreadyUpToDate`), so it can be larger than the count of underlying child workflows. doneCount: type: number description: >- Number of records that have reached a terminal state — `completed + failed + cancelled + alreadyUpToDate + blocklisted`. Use with `totalActions` to render `X/Y done`. statusCounts: type: object properties: pending: type: number description: Number of pending actions processing: type: number description: Number of processing actions completed: type: number description: >- Number of successfully completed actions, excluding blocklisted entities. failed: type: number description: Number of failed actions queued: type: number description: Number of queued actions cancelled: type: number description: Number of cancelled actions alreadyUpToDate: type: number description: >- Number of records the worker skipped because the contact/company was already in the workspace and up to date. blocklisted: type: number description: >- Number of completed actions whose target contact/company is on the workspace blocklist. Subset of `completed` already deducted from that bucket so the buckets sum to `totalActions`. required: - pending - processing - completed - failed - queued - cancelled - alreadyUpToDate - blocklisted progress: type: number minimum: 0 maximum: 100 description: >- Completion percentage (0-100) — `doneCount / totalActions`. createdAt: type: string format: date-time description: Date and time when the actions group was created lastUpdatedAt: type: string format: date-time description: >- Most recent timestamp across every underlying workflow (falls back to `createdAt` when no workflow has updated yet). Use it to detect staleness: if this stays unchanged for an extended period while `overallStatus` is `PROCESSING` or `QUEUED`, the run may be stuck behind a worker backlog rather than actively progressing. required: - actionsId - entity - overallStatus - totalActions - doneCount - statusCounts - progress - createdAt - lastUpdatedAt required: - status - message - data '400': description: Bad request - invalid actionsId parameter '404': description: Actions group not found security: - apiKey: [] components: securitySchemes: apiKey: type: apiKey in: header name: x-api-key ````