---
title: "Get an execution log"
method: GET
path: "/gdc/projects/{projectId}/dataload/processes/{processId}/executions/{executionId}/log"
tags: ["execution"]
---

# Get an execution log

`GET /gdc/projects/{projectId}/dataload/processes/{processId}/executions/{executionId}/log`

## Request

- Base URL: `https://secure.gooddata.com`
- URL: `https://secure.gooddata.com/gdc/projects/{projectId}/dataload/processes/{processId}/executions/{executionId}/log`
- Auth: none declared

Add an `Accept:text/plain` header, and specify a range header to retrieve only part of an execution log (`Range:0-999`). If you do not specify a range, the response returns `200 OK` and the full log in the response body. If the provided range is not valid, the response returns `416 Requested Range Not Satisfiable`.

## Response `200`

OK - Client didnt send Range header, whole actual log content is returned as text/plain

## Other responses

- `206`: Partial Content - Client sent Range header with proper start offset. Appropriate part of content length is returned as text/plain with proper Content-Range header. Content-Range /* indicates that log file is still incomplete, /<final_log_length> indicates that log file is complete
- `404`: Not Found - If given execution or its log does not exist
- `416`: Requested Range Not Satisfiable - Client sent Range header with invalid offset. Content-Range header will be set in response. Content-Range /* indicates that log file is still incomplete, /<final_log_length> indicates that log file is complete

---

[API](https://skmtc.dev/gooddata/apis/gooddata-api-documentation.md) - [All operations](https://skmtc.dev/gooddata/apis/gooddata-api-documentation/llms.txt) - [OpenAPI document](https://skmtc.dev/gooddata/apis/gooddata-api-documentation/revisions/e5dc0ee6ab00?raw)