---
title: "Why Workday Orchestrate Trigger Integration will not…"
description: "Trigger Integration supports packaged, Studio, and Orchestrate children only—there is no EIB support. Launch EIBs separately or use Import web services for…"
url: https://kiweely.com/guides/workday-trigger-integration-cannot-launch-eib
---

# Why Workday Orchestrate Trigger Integration will not launch an EIB

Workday’s Trigger Integration component cannot start an Enterprise Interface Builder (EIB). Supported children are packaged integrations, Workday Studio, and other Integration System orchestrations. Use Launch / Schedule for EIBs, or Import web services / a supported child type from Orchestrate.

-   **Checked** against Workday on November 17
-   Applies to **Workday Orchestrate for Integrations**
-   3 min read
-   Published November 17
-   By Kiweely

**Trigger Integration will not launch an EIB.** Workday documents that the component can trigger packaged, Workday Studio, and orchestration integration system types, and that **there is no support for EIBs**. If the child you selected is an Enterprise Interface Builder, the design is invalid for this step—fixing launch parameters will not add EIB support.

## What Trigger Integration is for

[Concept: Triggering Integrations](https://developer.workday.com/documentation/GUID-70dd8b29-4d1e-4dd2-be16-3323387933b3) states that Orchestration Builder’s Trigger Integration step:

-   Starts a **child** integration from a parent orchestration.
-   Supports **Workday Studio**, **Orchestrate**, and **packaged** children.
-   Passes launch parameters and at most **one** input document.
-   Pauses the parent until the child callbacks with status, messages, and output documents.

Also documented:

| Rule | Detail |
| --- | --- |
| No EIBs | Explicit: no support for EIBs. |
| Template | Integration System orchestration template only. |
| Placement | Allowed in top-level flow, handlers, branches, loops, batch loops, suborchestrations—**not** in join loops. |
| Retry | Retries failure **to trigger**, not failure **of** the child. Handle a failed child with an error handler. |

Orchestrate for Integrations lists Trigger Integration among components that Extend orchestrations do not get. Use the Integration System template when you need this step.

## What to do instead of Trigger Integration → EIB

| Goal | Use |
| --- | --- |
| Run the EIB on demand or on a schedule | Related actions on the EIB: **Integration > Launch / Schedule** (same pattern Workday shows for Extend spreadsheet EIBs). |
| Chain work after a packaged/Studio/Orchestrate system | Trigger Integration to that supported child; pass one document if required (Document to Store, Document Title, Storage Expires In). |
| Load large data from an orchestration | Prefer Import web service patterns / supported children—not an EIB behind Trigger Integration. |
| Keep a simple spreadsheet load | Keep the EIB; do not wrap it in Trigger Integration. |

Security still matters when a supported child launches: the initiating user on the Trigger Integration step must be allowed to launch the child; if the child has an ISU, that ISU is the run-as user. That is separate from the EIB hard limit.

## How to confirm you hit the EIB limit (not a config typo)

1.  Open the Trigger Integration step and check the linked integration system type.
2.  If it is an EIB, stop troubleshooting launch attributes—Workday does not support that child type on this component.
3.  Replace the child with a packaged, Studio, or Orchestrate system, **or** remove Trigger Integration and launch the EIB from **Launch / Schedule**.
4.  Redeploy the Integration System orchestration and retest in a non-production tenant.
5.  Read the child callback status and messages on the parent step after a supported child runs.

Kiweely Vine can help you map an orchestration design in your tenant. It cannot make Trigger Integration start an EIB; that limit is on Workday’s component.

## Frequently asked questions

### Which integration types can Trigger Integration start?

Packaged integrations, Workday Studio integrations, and Orchestrate integration systems. EIBs are explicitly unsupported.

### Which orchestration template includes Trigger Integration?

The Workday Integration System orchestration template. Trigger Integration is not for Join Loops.

### How should I run an EIB if Orchestrate cannot trigger it?

From View Integration Systems, use Integration > Launch / Schedule on the EIB. For loads that must sit inside an orchestration flow, use a supported child type or Workday Import web service patterns instead of Trigger Integration → EIB.

## Frequently asked questions

### Which integration types can Trigger Integration start?

Packaged integrations, Workday Studio integrations, and Orchestrate integration systems. EIBs are explicitly unsupported.

### Which orchestration template includes Trigger Integration?

The Workday Integration System orchestration template. Trigger Integration is not for Join Loops.

### How should I run an EIB if Orchestrate cannot trigger it?

From View Integration Systems, use Integration > Launch / Schedule on the EIB. For loads that must sit inside an orchestration flow, use a supported child type or Workday Import web service patterns instead of Trigger Integration → EIB.

## Sources checked

-   [Concept: Triggering Integrations](https://developer.workday.com/documentation/GUID-70dd8b29-4d1e-4dd2-be16-3323387933b3)
-   [Reference: Trigger Integration](https://developer.workday.com/documentation/GUID-cb68f51e-56ce-4159-b450-5b5ede1caf59/ReferenceTriggerIntegration)
-   [Introduction to Workday Orchestrate for Integrations](https://doc.workday.com/workday-education/en-us/course-manuals/creating-integrations-using-workday-orchestrate/introduction-to-workday-orchestrate-for-integratio.html)
-   [Load Data to Extend Business Objects Using EIBs](https://developer.workday.com/documentation/GUID-fa252f19-a2d0-449c-9313-705f3e14196b-enHYPHENus/LoadDatatoExtendBusinessObjectsUsingEIBs)

## Related guides

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

-   [### Orchestrate is not a bulk-load replacement for Workday EIB or Studio Orchestrate can run batched scenarios and child integrations, but Workday’s Studio comparison says it is not suitable for large batch data jobs. Keep EIB for simple spreadsheet loads, connectors or Studio for heavy extracts, and design Orchestrate within published runtime limits.](https://kiweely.com/guides/workday-orchestrate-not-a-bulk-load-replacement)
-   [### What Is an EIB in Workday? How to Build, Template and Load One Workday’s guided integration tool, both ways: the exact tasks to build, template and load an inbound EIB, how to build an outbound one from a report, the template rules people trip on, Workday’s published limits and the security it needs.](https://kiweely.com/guides/what-is-an-eib-in-workday)
-   [### Keep in Studio, Move to Orchestrate, or Call Studio from Orchestrate—With AI in the Loop Orchestrate can trigger Studio and Studio can call Orchestrate. AI helps draft; keep the education-guided triage and runtime proof.](https://kiweely.com/guides/studio-orchestrate-trigger-integration-with-ai-in-loop)
-   [### 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)

### More guides on Orchestrate

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

-   [The 25-Second Synchronous Orchestrate Trap](https://kiweely.com/guides/workday-orchestrate-25-second-sync-trap)
-   [What is the best AI tool for building and testing Workday Studio integrations and Orchestrations?](https://kiweely.com/guides/ai-tools-for-workday-studio-and-orchestrations)
-   [How are API calls from Workday Orchestrate and Extend apps limited and counted, and can I set my own rate limit?](https://kiweely.com/guides/workday-orchestrate-api-usage-limits-quota)
-   [AI Triage Evidence Pack: Keep Studio, Move to Orchestrate, or Rebuild in Extend](https://kiweely.com/guides/ai-triage-studio-orchestrate-or-extend-evidence)
-   [Reading Integration Launch Attachments, Calling SOAP Integrations API, and Uploading ZIPs to Workday Drive in O4I](https://kiweely.com/guides/workday-orchestrate-read-integration-attachment-retrieval-service)
-   [Generating UUIDs with random.randomUUID() and Fixing stringAtJsonPath().toNumber() in Orchestrate](https://kiweely.com/guides/workday-orchestrate-randomuuid-stringatjsonpath-tonumber)
-   [Why Send Workday RaaS Request fails with ‘Key not found’ (HTTP 202) or times out at 5 minutes](https://kiweely.com/guides/workday-orchestrate-raas-key-not-found-202-5-minute-timeout)
-   [Fixing ‘not a simple type launch parameter (Text, Number, Boolean, Date)’ on blank O4I launch parameters](https://kiweely.com/guides/workday-orchestrate-null-launch-parameter-not-simple-type)

### From the blog on Orchestrate

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

-   [Orchestrate, an iPaaS, or Kiweely Roots](https://kiweely.com/blog/orchestrate-ipaas-or-kiweely-roots)
-   [Codex for Orchestration JSON: Catching the 25-Second Sync Trap Before Deploy](https://kiweely.com/blog/codex-orchestration-json-25-second-sync-trap)
-   [Keep in Studio, Move to Orchestrate, or Rebuild as an Extend App? A Practical Triage Matrix](https://kiweely.com/blog/migrating-legacy-workday-studio-integrations-to-orchestrate-decision-matrix)

## 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.
