---
category: [Administration & Integrations, Platform and Product Extensions, Platform and Product Extensions/Integration, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions/Workday Extend]
keyword: [Extend, Orchestration Builder, Orchestrate, Orchestration]
nav: wcp_docs
parent_url: /wcp_docs/
title: Debug Orchestrations
layout: subsection
---

### Prerequisites

Create an orchestration.

### Context

Orchestration Builder's debugging tool enables you to quickly identify and resolve issues by running an orchestration, suborchestration, or error handler one step at a time. You can provide input and inspect output at each step, enabling you to pinpoint sources of unexpected output, so you can make appropriate adjustments.

<b>Note:</b> Debugging is currently unavailable for use with these components:

-   <b>Trigger Business Process</b>


-   <b>Trigger Integration</b>
-   <b>Trigger PDF Generation</b>


Debugging is also unavailable with <b>Send HTTP Request</b> components that make use of polling.

### Steps

1.  Open the orchestration that you want to debug.

    <b>Note:</b> If an orchestration meets any of these criteria, you must deploy its app to a tenant and run it at least once before you can debug:

    -   Built on the Workday Integration System template.
    -   Contains a suborchestration that references the `lp` or `intsys` methods.
    -   Contains a suborchestration that uses any of these components:

        -   Trigger PDF Generation
        -   Store Document
        -   Log to File
        -   Add Integration Message


2.  Select the step where you want to begin the debugging process.
3.  On the right of the properties panel, click <b>Debug Step</b>.

    You can switch back to the properties panel by clicking <b>Edit Properties</b>.

4.  Click <b>Select Tenant</b> and choose the tenant where the app is deployed.
5.  Click <b>Connect to Tenant</b>.
6.  In the <b>Debugging</b> panel, Orchestration Builder displays the name of the connected tenant alongside the name of the current step. To switch to a different tenant where the app is deployed, click <b>Manage Connections</b> at the top of the panel.
7.  If you haven't run the preceding step or if this is the first step in the orchestration, you must supply the step inputs manually.

    In the <b>Required Inputs</b> section, use the <b>Value</b> expression field to provide <b>Name</b> and <b>Data type</b> .

    <b>Note:</b> When you debug an orchestration that meets any of the criteria listed in step 1, Orchestration Builder asks you to select a recent app run from the tenant. Doing so enables the importation of the relevant integration's launch parameters and authentication tokens, along with any associated documents.

8.  Click <b>Debug Current Step</b>.
9.  Orchestration Builder runs the step and displays its <b>Debug Outputs</b>. Inspect them to make sure they're as expected.
10. Click <b>Next Step</b>.

    Because you ran the previous step, Orchestration Builder displays values for this step's <b>Required Inputs</b>.

11. Click <b>Debug Current Step</b> and once again, examine the <b>Debug Outputs</b>.


### Next Steps

<a id="postreq_1"></a>
Repeat the process of selecting a first step to debug, providing its required inputs if necessary, running it, and advancing to the next step, checking output data as you proceed.