---
category: [Administration & Integrations, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions, Platform and Product Extensions/Integration]
keyword: [Integrate, Workday Integration, Orchestrate for Integrations, Orchestration, Orchestration Builder]
nav: wcp_docs
parent_url: /wcp_docs/
title: >- 
  Reference: Call Suborchestrations
layout: subsection
---

## Purpose

Use this component to call a suborchestration that's part of the same app. Orchestration Builder displays a separate instance of the component for each available suborchestration. Examples: Call CustomerDetails, Call CreatePDF.

<b>Note:</b> Suborchestrations with connector actions can only be called from orchestrations built on the Custom Agent Action template. Calling them from orchestrations built on other templates causes build failure.

## <a id="d296e108"></a>Template Availability

This component is available in these orchestration templates:

-   Synchronous
-   Asynchronous
-   Business Process
-   Home Card
-   Integration System
-   Custom Agent Action


## <a id="d296e136"></a>Properties

The <b>Inputs</b> section displays the inputs that you configured for the suborchestration. See [Add Suborchestrations](/wcp_docs/GUID-53b9199b-89aa-4f65-98b4-dab35fd36218-enHYPHENus.html).

Provide a <b>Value</b> for each <b>Key</b>. The values you provide are passed to the suborchestration when you call it.

For reference, Orchestration Builder also displays the outputs you configured for the suborchestration.

There are several reasons why you might want to delay the launch of a suborchestration. Examples: to allow for latency in external systems, to allow external databases time to index, to accommodate long-running exports that lack a completion signal.

To add a launch delay for the suborchestration, first select the <b>Advanced Mode</b> checkbox. Under the<b>Suborchestration Launch Delay</b> heading that now displays, use the <b>Delay Duration (Minutes)</b> expression field to provide a delay. Enter a literal number, or an expression that evaluates to NumberType at runtime. The allowed range is 1 to 60 minutes. If an expression evaluates outside this range, its value is changed to the nearest boundary. Examples: an evaluated value of 65 minutes becomes a 60-minute delay, 30 seconds becomes a 1-minute delay.

The delay is always applied at the start of the suborchestration invocation, never at the end.

<b>Note:</b> Suborchestration launch delays aren't available in synchronous orchestrations or from Join loops.