---
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, Orchestrate, Runtime, Limits]
nav: wcp_docs
parent_url: /wcp_docs/
title: >- 
  Reference: Orchestration Runtime Limits
layout: subsection
---

## <a id="orchexectimeouts"></a>Orchestration Execution Timeouts

<table><thead><tr><th>Type</th><th>Limit</th><th>Description</th></tr></thead><tbody><tr><td>Workday Home Card orchestration runtime duration</td><td>5 minutes</td><td>The total processing time allowed for a Home Card orchestration.</td></tr><tr><td>Synchronous orchestration runtime duration (Extend apps only)</td><td>5 minutes</td><td>The total processing time allowed for a synchronous orchestration.</td></tr><tr><td>Asynchronous orchestration runtime duration  (Extend apps only)</td><td>48 hours</td><td>The total processing time allowed for an asynchronous orchestration. </td></tr><tr><td>Workday Integration System orchestration runtime duration</td><td>48 hours</td><td>The total processing time allowed for an Integration System orchestration.</td></tr><tr><td>Workday Business Process orchestration runtime callback period</td><td>90 days</td><td>The period during which a Business Process triggered by an orchestration must complete.</td></tr><tr><td>Recursive self-calls from a synchronous orchestration</td><td>31 iterations</td><td>The number of times a synchronous orchestration can call itself before failing.</td></tr><tr><td>Connector action</td><td>5 mins</td><td>The total processing time allowed for a Connector action.</td></tr></tbody></table><br/>

## <a id="orchprocexectimeouts"></a>Process Execution Timeouts

<table><thead><tr><th>Type</th><th>Limit</th><th>Description</th></tr></thead><tbody><tr><td>Individual process (Prod)</td><td>60 minutes</td><td>The maximum time allowed for any process in an app that's been promoted to a production tenant. For more information, see: <a href="/wcp_docs/GUID-9473ecbe-0243-41f0-9fe6-fc015e468a56.html">Concept: Orchestration Processes</a>.</td></tr><tr><td>Individual process (Nonprod)</td><td>45 minutes</td><td>The maximum time allowed for any process in an app that hasn't been promoted to a production tenant. For more information, see: <a href="/wcp_docs/GUID-9473ecbe-0243-41f0-9fe6-fc015e468a56.html">Concept: Orchestration Processes</a>.</td></tr></tbody></table><br/>

## <a id="orchdatamemlimits"></a>Data and Memory Limits

<table><thead><tr><th>Type</th><th>Limit</th><th>Description</th></tr></thead><tbody><tr><td>Concurrent data in memory</td><td>200 MB</td><td>The maximum amount of data an orchestration can have in memory at the same time. <p>The figure includes the data held by all in-scope values in memory as well as any temporary values created while evaluating expressions. It doesn't include the heap space taken up by an orchestration.</p> <p>Note that Workday manages large data items on disk in file-backed data structures. This feature means that an orchestration can have many values that are larger than the 20 MB limit in scope concurrently because they're not held in memory.</p></td></tr><tr><td>Concurrent data on disk</td><td>2 GB</td><td>The maximum amount of data an orchestration can have on disk in file-backed data structures at the same time. <p>Note that once values go out of scope, they're cleaned up by the runtime. Any associated data on disk no longer counts towards this limit.</p></td></tr><tr><td>Connector action input file</td><td>128 MB</td><td>The maximum size for a file used as input for a Connector action.</td></tr></tbody></table><br/>

## <a id="orchmesssizelimits"></a>Message Size Limits

<table><thead><tr><th>Type</th><th>Limit</th><th>Description</th></tr></thead><tbody><tr><td>Launch message size</td><td>20 MB</td><td>The maximum size of the request message used to launch an orchestration.</td></tr><tr><td>Response message size</td><td>500 MB</td><td>The maximum size of an individual HTTP message response returned from an HTTP API call.</td></tr></tbody></table><br/>

## <a id="orchstructlimits"></a>Orchestration Structure Limits

<table><thead><tr><th>Type</th><th>Limit</th><th>Structure</th></tr></thead><tbody><tr><td>Synchronous orchestration triggered by a presentation page</td><td>25 seconds</td><td>The total processing time allowed for a synchronous orchestration triggered by a presentation page. Takes precedence over any timeouts you configured on the orchestration itself. If you anticipate a total processing time of longer than 25 seconds, Workday recommends that you use an asynchronous orchestration.</td></tr><tr><td>Orchestrations and suborchestrations in an app</td><td>150</td><td>The total number of orchestrations and suborchestrations allowed in a single app. Extend warns you when the total reaches 125.</td></tr><tr><td>Steps in an orchestration</td><td>300</td><td>The total number of steps allowed in an individual orchestration. Extend warns you when the total reaches 200.</td></tr></tbody></table><br/>