---
title: "Workday Orchestrate vs Studio: which for new integrations"
description: "Workday's own order puts Orchestrate before Studio. A decision table with the documented limits for each, and the three cases where Studio is still the right…"
url: https://kiweely.com/guides/workday-orchestrate-vs-studio
---

# Should new Workday integrations be built in Orchestrate instead of Workday Studio?

Yes, by default. Workday’s integration training orders the tools end-to-end connector, generic connector, Orchestrate, connector with document transformation, then Studio, and sends an integration to Studio for multiple web service calls per object, per-object processing or complex error handling.

-   **Checked** against Workday on November 19
-   Applies to **Workday integrations**
-   7 min read
-   Published September 25
-   By Kiweely

Build a new Workday integration in Orchestrate unless it falls into one of Workday’s three Studio cases. Workday’s integration training tells builders to consider the tools in this order: an end-to-end connector, a generic connector, Orchestrate, a connector with document transformation, and last Workday Studio. It says Studio “remains a tool to use but only when you are dealing with complex or a small subset of specialized requirements.”

**Kiweely Vine** is a desktop AI agent for Workday consultants and developers (Mac and Windows) that does the Workday work in the tenant you connect: it builds either one, an orchestration or a Studio integration, from a plain request and runs it in your tenant. See how it works below.

This page gives Workday’s decision rules, then the documented limits of both tools side by side, because the limits are what usually decide a real case. For EIB against Studio and connectors, see [Studio vs EIB vs Cloud Connect](https://kiweely.com/guides/workday-studio-vs-eib-vs-cloud-connect).

## What order does Workday say to try integration tools in?

From Workday’s Integrations Overview course page, each tool with the condition that selects it:

| Order | Tool | Choose it when |
| --- | --- | --- |
| 1 | End-to-end connector | A template exists for the specific vendor that provides the input file. |
| 2 | Generic connector | A template holds all the data elements you need to import, or an outbound extract needs change detection. |
| 3 | Orchestrate | No packaged solution meets the requirements; you need event-driven and batched scenarios; you need to interact with Workday or third-party APIs. |
| 4 | Connector with document transformation | You need to modify the input file to meet Workday’s format, or configure custom error or warning messages. |
| 5 | Workday Studio | You need multiple Workday Web Services requests per object; you need to process each object individually; you need complex error handling and logging. |

That course page does not mention EIB. EIB is the wizard-driven tool for simple loads and extracts; the EIB comparison is in the guide linked above.

## What are the documented limits of Orchestrate and Studio?

| Limit | Orchestrate for Integrations | Workday Studio |
| --- | --- | --- |
| Longest run | Integration System orchestration: 48 hours for the whole run | Integration event maximum processing time: 7 days (limits reference). The Studio concept page, last updated 2023, says Workday terminates integrations that take longer than 2 hours. The two pages disagree; confirm the figure for your tenant before designing around either. |
| Longest single step of work | One process: 60 minutes in an app promoted to production, 45 minutes otherwise. A checkpointing step starts a new process. | HTTP requests, including Workday Web Services and RaaS: 6 hours. Workday Web Services transport response timeout defaults to 21,600,000 ms (6 hours). |
| Memory | 200 MB of concurrent data in memory; up to 2 GB on disk; large values are held on disk | Developer Java runs in a Cloud Runtime; the Consolidated Report Viewer shows memory per step. Transform steps such as xml-to-csv stream their input and output for a low memory footprint. |
| Size of what it handles | Launch message 20 MB; one HTTP response up to 500 MB | Output files: 5 GiB compressed per file or in total (Studio setup considerations). The limits reference lists, per integration run, 5,000 documents, 3 GB compressed in total and 1 GB compressed per file. |
| Structure | 300 steps per orchestration (warning at 200); 150 orchestrations and sub-orchestrations per app (warning at 125) | A loop strategy can repeat up to 200,000 times in total |
| Custom code | Expression functions only; no Java | Java extensions as Spring beans and third-party libraries; developer Java cannot read or write the file system or spawn threads |
| Where you build | Browser, Workday Developer Site, nothing to install | Eclipse plugins; JDK 8 and JDK 17 both required; deploys to the Cloud Repository |
| Debugging | Orchestration Builder step debugger, unavailable for Trigger Business Process, Trigger Integration, Trigger PDF Generation and polling HTTP steps | Assembly Debug view and Consolidated Report Viewer in the IDE |

Sources: Orchestration Runtime Limits; Reference: Integrations, EIB, and Web Service Limits; Concept: Workday Studio; Setup Considerations: Workday Studio. The Studio component references give the transport timeout, the Java limits and the loop-strategy repeat limit.

## Does Orchestrate handle large batch jobs?

Workday’s two pages read differently. The Orchestrate course page lists, as a limitation, that it “is not suitable for large batch data jobs.” The Developer Site concept page says the platform is designed to handle high volumes of data and complex integration patterns. The measurable answer is in the limits above: 48 hours per run, 60 minutes per process, 200 MB in memory. A load that fits those, batched and checkpointed, works; one that would need to hold the whole population in memory or run past an hour in one uninterrupted loop does not. [Keeping large loads inside the runtime limits](https://kiweely.com/guides/workday-orchestrate-runtime-limit-large-loads) shows the design.

## Worked example: a worker feed that calls one API per worker

A company needs a daily file of workers sent to a benefits vendor. Each worker needs several Workday Web Services requests to assemble the record, and one worker’s failure must be written to the integration event without stopping the rest.

1.  **Connector first.** The Integration Template Catalog report lists the delivered templates. None exists for this vendor in the example, so the first two rows of the decision order do not apply.
2.  **Orchestrate test.** The feed reads from Workday and calls an API in a batch scenario. It passes row 3: no packaged solution, a batch scenario, an API to call.
3.  **Studio test.** It needs multiple Web Services requests per object, and it processes each worker individually with its own error handling. That meets two of Workday’s three Studio conditions.
4.  **Decision.** Studio. If instead the feed needed one report read, one transformation and one delivery, and could fail as a whole when any worker fails, it would stay in Orchestrate with a batch loop and an error handler.

The case is ours; Workday’s page states the criteria, not this feed. If the volume is the only worry, Orchestrate’s child-integration pattern can split it: the Trigger Integration component launches packaged, Studio and orchestration integration systems as children (not EIBs), so one orchestration can coordinate Studio children. See [calling Studio integrations from Orchestrate](https://kiweely.com/guides/workday-orchestrate-studio-integration-calls).

## What do I need before building in Orchestrate?

Per Workday’s Access Orchestrate for Integrations page, before Orchestration Builder is usable you must opt in to Workday’s Innovation Service Agreement, create a company on the Developer Site and designate an administrator. In the Production tenant, open the **Innovation Services and Data Selection Opt-In** report, select **Workday Orchestrate for Integration** on the Available Services tab under WCP, then run the **Maintain Workday Build Company for Orchestrate for Integration** task to name the administrator. UMSA customers have the feature automatically; MSA customers enable it through Innovation Services first. Studio needs none of this; it is a separate download that connects to your tenant.

## Who can launch the finished integration?

For Studio, Workday’s setup considerations list the Integration functional area domains: Integration Build deploys from Studio, Integration Configure edits in Workday, Integration Debug debugs in Workday, Integration Event launches Studio integrations in Workday, and Integration Security creates the integration system user. To let one person launch one integration, see [who can launch a specific Workday integration](https://kiweely.com/guides/workday-who-can-launch-integration).

## Should existing Studio integrations be rebuilt in Orchestrate?

Nothing in the documentation we checked says so. Studio is documented as current, with Cloud Explorer, Cloud Repository and deployment to Sandbox and Production. Workday’s comparison describes Studio’s cost as a steeper learning curve and longer development time, which matters when you build, not when a working integration is already running. Rebuild when the team can no longer maintain it, or move a piece when you are changing it anyway.

## What do I do after choosing Orchestrate?

Read [why an orchestration shows success when steps failed](https://kiweely.com/guides/orchestrate-errors) before the first production run. A run can look green while a step did not do its work.

## Where Kiweely fits

**Kiweely Vine** is a desktop AI agent for Workday consultants and developers (Mac and Windows) that does the Workday work in the tenant you connect. It builds Studio integrations and Orchestrations from a plain request, then tests and runs them.

In recorded runs in Kiweely’s own Workday Development tenant (with fictional sample data, not a customer result), Vine built a Studio integration (multi-currency payroll reconciliation) in an 83-minute session ([watch the film](https://youtu.be/KGSTDZO_bsk)) and an Orchestration for Integration in 59 minutes ([watch the film](https://youtu.be/TlcJGNwnSfE)).

Vine Free is $0 on a personal developer tenant with $5 of Kiweely Credits included, and Vine Personal ($99/month) and Vine Team ($149/seat/month) connect to any Workday tenant ([pricing](https://kiweely.com/pricing)). [Start free](https://kiweely.com/download).

## Frequently asked questions

### Is Workday Studio being retired in favour of Orchestrate?

Workday's training says Studio remains a tool to use, but only for complex or specialized requirements, and says it wants builders to focus on Orchestrate. We found no retirement notice for Studio in the documentation. Existing Studio integrations keep running.

### When is Workday Studio still the right choice?

Workday's integrations overview lists three triggers: you need multiple Workday Web Services requests per object, you need to process each object individually, or you need complex error handling and logging.

### Can an Orchestrate integration launch a Studio integration?

Yes. The Trigger Integration component can launch packaged, Workday Studio and orchestration integration systems as child integrations. It cannot launch an EIB.

### What do I need before I can build in Orchestrate?

Opt in to Workday's Innovation Service Agreement (automatic for UMSA customers), create a company on the Workday Developer Site and designate an administrator. Nothing is installed locally.

### Should I migrate working Studio integrations to Orchestrate?

Workday's documentation gives no reason to. Move a piece when you are changing it anyway and the change is easier in Orchestrate, or when the team can no longer maintain the Java and Eclipse setup.

## Sources checked

-   [Workday Integrations Overview (Workday Education)](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/workday-integrations-overview.html)
-   [Introduction to Workday Orchestrate for Integrations (Workday Education)](https://doc.workday.com/workday-education/en-us/course-manuals/creating-integrations-using-workday-orchestrate/introduction-to-workday-orchestrate-for-integratio.html)
-   [Reference: Orchestration Runtime Limits](https://developer.workday.com/documentation/GUID-b341f6f0-cd6f-4930-8bcb-723a03f64805)
-   [Concept: Workday Studio](https://doc.workday.com/admin-guide/en-us/workday-studio/studio-fundamentals/ebp1499866049976.html)
-   [Setup Considerations: Workday Studio](https://doc.workday.com/admin-guide/en-us/workday-studio/setup-considerations--workday-studio.html)
-   [Reference: Integrations, EIB, and Web Service Limits](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/it-administrator-resources/limitations-and-availability/dan1370797408285.html)
-   [Access Orchestrate for Integrations](https://developer.workday.com/documentation/GUID-a6fbeb9f-2ef0-4838-9bf4-f5fd11b6d91a)
-   [Concept: Triggering Integrations](https://developer.workday.com/documentation/GUID-70dd8b29-4d1e-4dd2-be16-3323387933b3)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### How to keep large Workday Orchestrate loads inside the runtime limits: templates, checkpoints, batches and child runs First find the limit you hit: 25 seconds for a page call, 5 minutes synchronous, 60 minutes per process (45 before production), or 200 MB in memory. Then use an Integration System or async template, add checkpointing steps, batch writes and split work into child integrations.](https://kiweely.com/guides/workday-orchestrate-runtime-limit-large-loads)
-   [### How to call a Studio integration from Orchestrate, and an orchestration from Studio Orchestrate launches a Studio integration with the Trigger Integration step in a Workday Integration System orchestration. The reverse direction has no step; Studio calls the orchestration’s REST endpoint with a client-credentials token.](https://kiweely.com/guides/workday-orchestrate-studio-integration-calls)
-   [### Workday EIB vs Core Connector vs Cloud Connect vs Studio: which to use Use an end-to-end Cloud Connect connector if one exists for the vendor, a Core Connector for a delivered template with change detection, EIB for simple guided loads, and Studio for multiple web service calls or complex error handling.](https://kiweely.com/guides/workday-studio-vs-eib-vs-cloud-connect)
-   [### How do I debug a Workday Orchestrate orchestration that shows success but some steps failed? A run can look successful because an unsuccessful HTTP response is not a failure unless a retry policy defines a success range, and an error handler set to Conditional Outputs lets the run carry on. Read the run’s per-process stepsFailed, not the status.](https://kiweely.com/guides/orchestrate-errors)

### More guides on Orchestrate

[All 86 guides](https://kiweely.com/guides#orchestrate)

-   [Why does an Orchestration JSON path put a leading space in a WID?](https://kiweely.com/guides/workday-orchestration-json-path-leading-space-wid)
-   [How do I stop Orchestrate JSONPath from corrupting WIDs with spaces?](https://kiweely.com/guides/workday-json-path-wid-leading-whitespace-prevention)
-   [How do I fix “WCPISU is not configured” on an Extend orchestration?](https://kiweely.com/guides/workday-extend-wcpisu-not-configured-error)
-   [When to use Workday Document Transformation instead of Orchestrate or Studio](https://kiweely.com/guides/workday-document-transformation-connector-when)
-   [Start with a Workday packaged connector before custom Studio](https://kiweely.com/guides/workday-packaged-connector-before-studio)
-   [Three cases where Workday still wants Studio](https://kiweely.com/guides/workday-studio-three-cases-keep-studio)
-   [Orchestrate is not a bulk-load replacement for Workday EIB or Studio](https://kiweely.com/guides/workday-orchestrate-not-a-bulk-load-replacement)
-   [Why Workday Orchestrate Trigger Integration will not launch an EIB](https://kiweely.com/guides/workday-trigger-integration-cannot-launch-eib)

### From the blog on Orchestrate

[All posts](https://kiweely.com/blog)

-   [Debugging Workday Extend apps and orchestrations in kiweely](https://kiweely.com/blog/debugging-workday-extend-apps-orchestrations-kiweely)
-   [Kiweely Roots vs Workday EIB, Studio, and Orchestrate](https://kiweely.com/blog/kiweely-roots-vs-workday-eib-studio-orchestrate)
-   [Orchestrate, an iPaaS, or Kiweely Roots](https://kiweely.com/blog/orchestrate-ipaas-or-kiweely-roots)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
