Skip to content
KiweelyKiweelyKiweely

Overcoming ‘Message length should be lesser than 1MB in size’ and ‘Orchestration is too large to be saved’

Embedding a large BIRT .rptdesign XML layout in Create Text Template hits ‘Message length should be lesser than 1MB in size’, while large canvases hit ‘Orchestration is too large to be saved’. Load BIRT designs via intsys.attachmentContent(), delete disabled steps, and split into sub-orchestrations.

  • Checked against Workday on
  • Applies to Workday Orchestrate
  • 5 min read
  • Published
  • By Kiweely
On this page

Why Orchestration Builder rejects large templates and complex canvases

As your Workday Orchestrate flows grow or incorporate embedded XML/XSLT/BIRT report layouts, you can hit two distinct build-time and save-time size ceilings in Orchestration Builder:

  1. Message length should be lesser than 1MB in size — Thrown during validation or build when the static text inside a Create Text Template step (or the inline Message body of a Send Workday API Request / Send HTTP Request step) exceeds 1 MB. This happens frequently when pasting a BIRT .rptdesign XML layout (which often includes base64-encoded logos, embedded styles, and verbose table XML) directly into a template step to feed Trigger PDF Generation.
  2. Orchestration is too large to be saved. Reduce the scope or complexity of the Orchestration to enable saving. — Thrown when saving to App Hub because the serialized JSON/metadata definition of the orchestration canvas exceeds App Hub’s maximum persistence payload, or approaches the structural limit of 300 steps in an individual orchestration (with a warning at 200 steps, as listed in Reference: Orchestration Runtime Limits).

Splitting a >1 MB BIRT XML string across two or three Create Text Template steps inside the same orchestration still fails to save or build because all static string literals remain embedded inside the same serialized orchestration definition.

Fixing "Message length should be lesser than 1MB in size" for BIRT layouts

Never paste a large .rptdesign XML file or static XSLT document into a Create Text Template step. While a static template literal is capped below 1 MB, Orchestrate’s runtime streams binary and XML documents up to 200 MB in memory and 2 GB on disk when loaded dynamically at runtime.

In Orchestrate for Integrations (O4I), store the BIRT .rptdesign file on the Workday Integration System definition using an Integration Attachment Service, and read it at runtime with intsys.attachmentContent:

  1. In your Workday tenant, run Maintain Custom Integration Services on your Integration System and add a new Integration Attachment Service (for example, RPT_Design).
  2. Upload your .rptdesign XML file to the RPT_Design attachment service on the Integration System.
  3. In Orchestration Builder, delete the oversized Create Text Template step.
  4. Select your Trigger PDF Generation step (or an upstream Create Values step) and set the Report Design expression to read the attachment service content as XML:
javascript
intsys.attachmentContent("RPT_Design").asXML()

As documented in Reference: Intsys Global Functions, intsys.attachmentContent(attachmentServiceName: String) returns the binary Data of the attached file at runtime, and .asXML() casts it to the Xml type required by Trigger PDF Generation‘s Report Design property. Your orchestration definition shrinks from over 1 MB to a single line of expression code, and updating the BIRT layout later only requires replacing the attachment on the Integration System in the tenant.

Option 2: Fetch the design or template at runtime via Workday API or Drive

If you are building an Extend orchestration that does not run on an Integration System (or if you store shared templates centrally), store the .rptdesign or XML file in Workday Drive, an Extend Attachment Business Object, or a Business Form Layout, and fetch it at runtime using a Send Workday API Request step. As noted in Reference: Trigger PDF Generation, you can pass the output of an upstream Send Workday API Request step directly into the Report Design field.

Fixing "Orchestration is too large to be saved" in App Hub

When Orchestration Builder refuses to save an orchestration with Orchestration is too large to be saved. Reduce the scope or complexity of the Orchestration to enable saving, the serialized AST of every step, expression, mapping, and disabled component on the canvas has exceeded the per-orchestration storage limit.

Follow these three steps in order to bring the orchestration back under the limit:

1. Delete disabled test steps from the canvas

During development and debugging, developers often disable temporary Add Integration Message, Log, Log to File, Create Values, or Create Text Template steps rather than deleting them. Disabled steps are still serialized in full inside the orchestration definition when saving to App Hub. Deleting disabled Add Integration Message and test mapping steps is often enough by itself to allow the orchestration to save immediately.

2. Consolidate and streamline Create Values steps

Every key-value entry and nested conditional expression in a Create Values step adds AST nodes to the saved orchestration definition. As detailed in Concept: Optimizing Create Values Performance:

  • Remove unused intermediate variables from Create Values steps that are no longer referenced downstream.
  • Avoid duplicating large static lookup tables or multi-branch conditional assignments across multiple Create Values steps; use an Integration Map (intsys.mapAttributeValue or intsys.stringMapIterator) for tenant-configurable key-value lookups instead of hardcoding dozens of IF/ELSE conditions in Expression Builder.

3. Extract multi-step branches and loops into Sub-Orchestrations

Workday allows up to 150 orchestrations and sub-orchestrations in a single app (with a warning at 125) and up to 300 steps per individual orchestration (with a warning at 200). Each sub-orchestration is saved as its own separate definition in App Hub.

When an orchestration contains multiple complex Branch on Conditions paths or nested transformation steps:

  1. Create a new sub-orchestration in the Orchestrations panel (Add Suborchestrations).
  2. Configure the explicit input parameters on Start and output parameters on End.
  3. Move the transformation, validation, or API call steps from the main canvas into the sub-orchestration and replace them on the main canvas with a single Call Suborchestration step. (Remember that Send Workday RaaS Request and Trigger Business Process must remain in the parent orchestration.)

How to verify the fix in the tenant

  1. After externalizing large XML templates to intsys.attachmentContent("RPT_Design").asXML() and removing disabled steps, click Validate and save the orchestration to App Hub to confirm neither the 1 MB message error nor the save-size error occurs.
  2. Deploy the app to your tenant, confirm the .rptdesign file is attached to the RPT_Design service on the Integration System, and launch the integration.
  3. Verify on the Integration Event that Trigger PDF Generation renders and attaches the PDF (via your downstream Store Document step) with the exact layout from the attached .rptdesign file.

Sources checked

Related guides

All guides

Let Workday check the work.

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

Get the next guide in your inbox.

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

We’ll email you once to confirm. Unsubscribe in one click from any issue.