> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # Get Workflow Execution Results > Returns the outcome of one finished execution of the workflow named in the path: the final business output, the output of every step and, on failure, the error. Call it once the execution status is completed or failed. The final output is JSON by default; request XML with the `format=xml` query parameter (which wins) or an `Accept: application/xml` header. Read-only: nothing changes. The body is the same as GET /v1/executions/{id}/results; this operation additionally requires the execution to belong to the workflow in the path, so it is the one to use with a credential confined to some workflows. Errors: 400 FLK-0002 when workflowId or executionId is not a UUID; 404 FLK-0500 when no execution with this id belongs to that workflow — an execution of another workflow is answered exactly as one that does not exist; 422 FLK-0502 while the execution is still pending or running; 403 when the credential may not read executions of that workflow. ## OpenAPI ````yaml /pt/openapi/v3-current/flowker.yaml get /v1/workflows/{workflowId}/executions/{executionId}/results openapi: 3.1.0 info: description: >- Complete API reference for Flowker workflow orchestration services including catalog management, workflow definitions, executor configurations, provider configurations, and workflow executions. title: Flowker API version: 1.4.0 servers: - url: https://flowker.sandbox.lerian.net security: - BearerAuth: [] tags: - name: Catalog API description: >- Browse built-in providers, executors, and triggers available in the Flowker catalog. - name: Workflows API description: >- Create, update, activate, deactivate, clone, and delete workflow definitions. - name: Executions API description: Start workflow executions and track their status and results. - name: Executor Configurations API description: >- List, inspect, update, and delete the executor configuration records a deployment holds. - name: Provider Configurations API description: >- Create, update, enable, and disable the provider configurations that workflow nodes call through. - name: Dashboard API description: >- Retrieve aggregated summaries of workflows and executions for operational dashboards. - name: Webhooks API description: >- Receive webhook callbacks from external systems to trigger workflow executions. - name: Schedule API description: >- Inspect a workflow's upcoming, skipped, and parked scheduled occurrences, and run or discard the parked ones. - name: Schema Registry API description: >- Publish global OpenAPI specification versions for native services and pin the version each tenant resolves against. - name: OpenAPI Schemas API description: >- Upload, inspect, and delete the tenant's external OpenAPI schemas, and derive the contract of a single operation. - name: XSD Schemas API description: >- Upload, inspect, and delete the tenant's XSD schemas used to validate XML webhook payloads. paths: /v1/workflows/{workflowId}/executions/{executionId}/results: get: tags: - Executions API summary: Get Workflow Execution Results description: >- Returns the outcome of one finished execution of the workflow named in the path: the final business output, the output of every step and, on failure, the error. Call it once the execution status is completed or failed. The final output is JSON by default; request XML with the `format=xml` query parameter (which wins) or an `Accept: application/xml` header. Read-only: nothing changes. The body is the same as GET /v1/executions/{id}/results; this operation additionally requires the execution to belong to the workflow in the path, so it is the one to use with a credential confined to some workflows. Errors: 400 FLK-0002 when workflowId or executionId is not a UUID; 404 FLK-0500 when no execution with this id belongs to that workflow — an execution of another workflow is answered exactly as one that does not exist; 422 FLK-0502 while the execution is still pending or running; 403 when the credential may not read executions of that workflow. operationId: getWorkflowExecutionResults parameters: - description: Identifier (UUID) of the workflow the execution belongs to. in: path name: workflowId required: true schema: format: uuid type: string - description: >- Execution identifier (UUID), as returned when the workflow was executed. in: path name: executionId required: true schema: format: uuid type: string - description: >- Response representation of the final business output. 'xml' forces XML and wins over the Accept header; any other non-empty value forces JSON. When omitted, the representation is content-negotiated via the Accept header ('application/xml' selects XML; JSON is the default). in: query name: format schema: type: string example: xml responses: '200': content: application/json: schema: $ref: '#/components/schemas/ExecutionResultsOutput' application/xml: schema: $ref: '#/components/schemas/ExecutionResultsOutput' description: >- Indicates that the request was successful and the response contains the requested data. '400': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: Indicates that workflowId or executionId is not a UUID (FLK-0002). '403': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates that the credential may not read executions of that workflow. '404': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates that no execution with this id belongs to that workflow (FLK-0500). An execution of another workflow is answered exactly as one that does not exist. '422': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates that the execution is still pending or running and results are not yet available (FLK-0502). '500': content: application/problem+json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates an unexpected internal error. If this persists, please contact support. components: schemas: ExecutionResultsOutput: example: executionId: f7e6d5c4-b3a2-1098-7654-321fedcba098 workflowId: a1b2c3d4-e5f6-7890-abcd-ef1234567890 status: completed stepResults: - stepNumber: 1 stepName: Set Payment Output nodeId: set-output status: completed output: actionType: set_output output: status: received executedAt: '2026-03-17T14:35:00Z' durationMs: 0 finalOutput: status: received startedAt: '2026-03-17T14:35:00Z' completedAt: '2026-03-17T14:35:00Z' properties: completedAt: description: Timestamp when the execution finished. example: '2026-03-17T14:35:12Z' format: date-time type: string executionId: description: Unique identifier of the execution. example: f7e6d5c4-b3a2-1098-7654-321fedcba098 format: uuid type: string finalOutput: additionalProperties: true description: Aggregated output from the last step or the workflow's final result. example: status: received type: object startedAt: description: Timestamp when the execution started. example: '2026-03-17T14:35:00Z' format: date-time type: string status: description: Final status of the execution. example: completed type: string stepResults: description: Ordered list of results for each step executed. items: $ref: '#/components/schemas/StepResultOutput' type: array workflowId: description: ID of the workflow that was executed. example: a1b2c3d4-e5f6-7890-abcd-ef1234567890 format: uuid type: string type: object ErrorResponse: properties: code: description: Stable, machine-readable Flowker error code. example: FLK-0001 type: string detail: description: >- Human-readable explanation of this occurrence. Responses with a status of 500 or above carry a fixed generic message. example: name is a required field type: string errors: description: Per-field entries for a request that failed validation. items: $ref: '#/components/schemas/ErrorDetail' type: array instance: description: URI reference identifying this specific occurrence. example: /v1/workflows format: uri type: string status: description: HTTP status code. example: 400 type: integer title: description: >- Standard HTTP reason phrase for the status. It does not change per error code. example: Bad Request type: string type: description: >- URI reference identifying the error. Always the error catalog base followed by the code. example: https://errors.lerian.studio/v1/FLK-0001 format: uri type: string type: object StepResultOutput: properties: attempts: description: >- Number of calls Flowker sent to the network for this step. `0` when Flowker sent no call. example: 1 type: integer bodyFormat: description: >- `xml` when the provider answered in XML, whether or not Flowker could decode the answer. Absent for a JSON answer. example: xml type: string bodyParseError: description: >- Reason Flowker could not decode the provider's XML answer. The step still completes, and `output` carries no body. example: 'XML syntax error on line 1: unexpected EOF' type: string durationMs: description: Time taken to execute this step, in milliseconds. example: 0 type: integer errorClass: description: >- Category of the failure: `client_error`, `auth_error`, `transient`, `circuit_open`, or `timeout`. Present only on a failed step. example: client_error type: string errorMessage: description: Error message if the step failed. Null on success. type: string executedAt: description: Timestamp when this step was executed. example: '2026-03-17T14:35:02Z' format: date-time type: string nodeId: description: ID of the workflow node that was executed. example: set-output type: string output: additionalProperties: type: object description: Output data produced by this step. example: actionType: set_output output: status: received type: object rawBody: description: >- The provider answer as received, up to its first 8 KiB. Present when `bodyFormat` or `bodyParseError` is set. example: OK type: string requestFormat: description: >- Request format the node configures: `json`, `xml_converted`, or `xml_passthrough`. Absent when the node configures none. example: xml_converted type: string retried: description: Whether Flowker sent more than one network call for this step. example: false type: boolean status: description: 'Status of this step: `completed`, `failed`, or `skipped`.' example: completed type: string statusCode: description: >- HTTP status the provider returned. Absent when no HTTP response arrived. example: 422 type: integer stepName: description: Human-readable name of the step. example: Set Payment Output type: string stepNumber: description: Position of this step in the execution sequence (1-indexed). example: 1 type: integer type: object ErrorDetail: properties: location: description: Where the problem is, such as body.nodes or path.id. example: body.nodes type: string message: description: Description of the field-level problem. example: expected array length >= 1 type: string value: description: The value that caused the error, when it is safe to echo. type: object securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- JWT bearer token issued by the identity provider. Send it in the Authorization header as `Bearer `. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.