---
category: [Administration & Integrations, Platform and Product Extensions, Platform and Product Extensions/Integration, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions/Workday Extend]
nav: wcp_docs
parent_url: /wcp_docs/
title: >- 
  Concept: Orchestration Builder Logs
layout: subsection
---

You can access <b>Build Logs</b> and <b>Run Logs</b> in the footer of the Orchestration Builder interface.

Build Logs are generated when you save your orchestration to App Hub. They provide information about Workday Orchestrate's efforts to compile your orchestration so it can be run. If Orchestrate encounters problems, it tries to pinpoint the source of the difficulty. It may also provide warnings about aspects of your orchestration that don't produce fatal errors, but which may negatively impact performance.

Run Logs are generated when your orchestration runs on the tenant where it's deployed. They provide runtime information that enables you to monitor, troubleshoot, and debug the orchestration.

Orchestrate organizes Run Log information under these 2 headings, each with its own default set of displayed fields:

-   Run Logs
-   API Logs


To change the information associated with a heading, click the <b>Edit Fields</b> button to open the <b>Add or Remove Fields</b> pane, then select the data you'd like Orchestration Builder to display or hide.

Example: you select API Logs from the drop-down menu, then from the <b>Add or Remove Fields</b> pane, you clear the <b>wd_path</b> checkbox and select <b>wd_request_bytes</b>. Under the API Logs heading, Orchestration Builder no longer displays the URL path for the API request and now displays the size of the payload of the API request in bytes.

Enable the <b>Auto-Refresh</b> toggle to refresh the logs every 30 seconds. You can also manually <b>Refresh</b> at any time.

This table describes the fields that you can display in your Run Logs:

<table><thead><tr><th>Log Field</th><th>Description</th></tr></thead><tbody><tr><td><b>wd_affected_user_account</b></td><td>The user account affected by an action.</td></tr><tr><td><b>wd_api_client_id</b></td><td><p>The ID that's generated when you register your API client.</p></td></tr><tr><td><b>wd_api_type</b></td><td><p>The functional area endpoint for the API request.</p> <p>Examples:</p><ul><li><code>aos</code>
</li></ul><ul><li><code>wql</code>
</li></ul></td></tr><tr><td><b>wd_api_version</b></td><td><p>The API version in use.</p></td></tr><tr><td><b>wd_app_component</b></td><td><p>The component of the app.</p> <p>Possible values:</p><ul><li><code>abo</code> – Business Objects.
</li><li><code>attributeStore</code> – Attribute Store.
</li><li><code>ps</code> – Presentation Components.
</li><li><code>workflows</code> – Workday Orchestrate.
</li></ul></td></tr><tr><td><b>wd_app_id</b></td><td><p>The ID for the app.</p></td></tr><tr><td><b>wd_app_promotion_status</b></td><td><p>The status of your app in the promotion lifecycle.</p> <p>Possible values:</p><ul><li><code>RELEASE_CANDIDATE</code>
</li><li><code>RELEASED</code>
</li><li><code>SANDBOX_RELEASE</code>
</li></ul></td></tr><tr><td><b>wd_billed_request_bytes</b></td><td>The actual API request bytes for which Workday bills you based on your usage of the resize image feature on the fileUploader widget.</td></tr><tr><td><b>wd_category</b></td><td><p>The category of app log information.</p> <p>For Workday Orchestrate, the value <code>console</code> returns custom log messages from the log component.</p> <p>For Presentation Components, these are the possible values:</p><ul><li><code>console</code> – Returns custom log messages from a PMD script that calls the console logging methods. The <code>wd_level</code> depends on whether the PMD script called the debug, error, info, or warn method.
</li><li><code>mobile</code> – Returns log entries related to presentation components of a custom app when used in the Workday mobile app.
</li><li><code>pageError</code> – Returns page exception messages in the wd_message field. The <code>wd_level</code> is ERROR.
</li><li><code>pageError.script</code> – Returns PMD script exception messages in the wd_message field. The <code>wd_level</code> is ERROR.
</li><li><code>promotion</code> – Returns information about the promotion of an app during the app lifecycle.
</li><li><code>responseError</code> - Returns details about an endpoint that encountered an error, including the HTTP status code, request URL, method, and request headers.
</li><li><code>scriptUsage</code> – Returns CPU and memory usage information about a script execution. The <code>wd_level</code> is INFO.
</li><li><code>sourceUpload</code> – Returns information about the uploading of source code for an app to App Hub.
</li></ul></td></tr><tr><td><b>wd_client_ip</b></td><td>The IP address where the request originated.</td></tr><tr><td><b>wd_common_request_id</b></td><td><p>A random, unique ID that tracks an incoming HTTP request. This ID doesn't change throughout all downstream requests.</p> <p>Example: <code>VPS|5a438101-0f47-4cfa-a3a5-a84c13c3252b</code></p> <p>For requests made in App Preview, <b>wd_common_request_id</b> starts with <code>WCPUI-APP-PREVIEW</code>.</p></td></tr><tr><td><b>wd_date_time</b></td><td><p>The date and time of the API request.</p></td></tr><tr><td><b>wd_env</b></td><td><p>The tenant environment.</p> <p>Possible values:</p><ul><li><code>IMPL</code> – Implementation tenant.
</li><li><code>SANDBOX</code> – Sandbox tenant.
</li><li><code>PROD</code> – Production tenant.
</li><li><code>WCPDEV</code> – Workday Cloud Platform development tenant.
</li></ul> <p>When the app runs in App Preview with no tenant connection, the value is always <code>WCPDEV</code>.</p></td></tr><tr><td><b>wd_gateway_url</b></td><td><p>The Workday API gateway for the tenant.</p> <p>When the app runs in App Preview without tenant connection, this value is always blank.</p></td></tr><tr><td><b>wd_hostname</b></td><td><p>The host URL.</p> <p>Example: <code>api.workday.com</code></p> <p>When the app runs in App Preview, this value is populated in the <code>remote</code> log, but is always blank in the <code>access</code> log.</p></td></tr><tr><td><b>wd_http_method</b></td><td><p>The HTTP method for the API request.</p></td></tr><tr><td><b>wd_http_protocol</b></td><td><p>The HTTP version for the API request.</p></td></tr><tr><td><b>wd_level</b></td><td><p>A label that categorizes log entries by level of urgency for troubleshooting and debugging.</p> <p>Possible values:</p><ul><li><code>ERROR</code> – Categorizes logs for serious but nonfatal issues in the app.
</li><li><code>WARN</code> – Categorizes logs for potentially harmful behavior with the app.
</li><li><code>INFO</code> – Categorizes logs that provide information on the normal behavior of the app.
</li><li><code>DEBUG</code> – Categorizes logs with more granular information that you can use to debug the app.
</li></ul></td></tr><tr><td><b>wd_log_type</b></td><td><p>The type of logs returned.</p> <ul><li><code>access</code> – Log entries with information about client requests.
</li><li><code>app</code> – Log entries with debugging, informational, warning, or error messages related to an app request. For log entries related to Presentation Components, see the log categories in <b>wd_category</b>.
</li><li><code>audit</code> – Log entries that enable administrators to track changes to code.
</li><li><code>remote</code> – Log entries with information about requests to a remote service.
</li></ul></td></tr><tr><td><b>wd_message</b></td><td><p>Provides details on events for your app.</p> <p>For the Workday Orchestrate service, this field enables you to view log information about your orchestrations.</p></td></tr><tr><td><b>wd_page_id</b></td><td>The ID of a PMD file.</td></tr><tr><td><b>wd_path</b></td><td><p>The URL path for the API request.</p> <p>Example: <code>/common/v1/workers/me/organizations</code></p></td></tr><tr><td><b>wd_referer</b></td><td><p>The address of the previous page linked to the requested resource.</p></td></tr><tr><td><b>wd_request_bytes</b></td><td><p>The size of the payload of the API request in bytes.</p></td></tr><tr><td><p><b>wd_request_content_type</b></p></td><td><p>The content type of the HTTP request.</p> <p>Example: <code>application/json</code></p></td></tr><tr><td><b>wd_resource</b></td><td><p>The resource of the RESTful API type.</p> <p>Example: <code>workers</code></p></td></tr><tr><td><p><b>wd_response_bytes</b></p></td><td><p>The size of the payload of the API response in bytes.</p></td></tr><tr><td><p><b>wd_response_code</b></p></td><td><p>The API response code.</p></td></tr><tr><td><b>wd_response_content_disposition</b></td><td><p>The content disposition header of the HTTP response.</p> <p>Example: <code>attachment; filename=Alerts.json</code></p> <p>When the app runs in App Preview, this value is always blank.</p></td></tr><tr><td><b>wd_response_content_type</b></td><td><p>The content type of the HTTP response.</p></td></tr><tr><td><b>wd_response_time</b></td><td><p>The total roundtrip time for the API request and response.</p> <p>When the app runs in App Preview without tenant connection, this value is always 0.</p></td></tr><tr><td><b>wd_service</b></td><td><p>The Workday service for the logs.</p> <p>Available Workday services:</p><ul><li>API Gateway (<code>api-gateway</code>).
</li><li>Workday Orchestrate (<code>orchestrate</code>).
</li></ul><p><b>Note:</b> An additional service, Presentation Components (<code>vps</code> or <code>wcpui</code>) is available to Extend app developers but not to integration app developers.</p></td></tr><tr><td><b>wd_session_id</b></td><td><p>The unique ID for a session.</p></td></tr><tr><td><b>wd_sku</b></td><td><p>The Workday product associated with the log.</p></td></tr><tr><td><b>wd_subresource</b></td><td><p>The subresource of the RESTful API type.</p> <p>Example: <code>organizations</code></p></td></tr><tr><td><b>wd_tenant</b></td><td><p>The tenant name.</p> <p>When the app runs in App Preview without tenant connection, this value is always blank.</p></td></tr><tr><td><b>wd_tenant_alias</b></td><td><p>The tenant alias name. You provide the tenant alias name during the Onboarding process.</p> <p>When the app runs in App Preview without tenant connection, this value is always blank.</p></td></tr><tr><td><b>wd_user_agent</b></td><td><p>The browser type and version in use.</p></td></tr><tr><td><b>wd_username</b></td><td><p>The developer username.</p></td></tr><tr><td><b>wd_orch_name</b></td><td>The name of the orchestration.</td></tr><tr><td><b>wd_orch_id</b></td><td>The ID of the orchestration.</td></tr><tr><td><b>wd_orch_step_name</b></td><td>The name of the orchestration step the log item refers to.</td></tr></tbody></table><br/>