---
title: "Debugging Workday Extend apps and orchestrations in kiweely"
description: "How kiweely unifies presentation, model, and orchestration debugging in Workday Extend, replacing manual log hunts with automated diagnosis."
url: https://kiweely.com/blog/debugging-workday-extend-apps-orchestrations-kiweely
---

# Debugging Workday Extend apps and orchestrations in kiweely

Traditional Extend debugging means jumping between Developer Site, tenant logs, and Orchestration Studio. kiweely connects the whole chain.

-   By Kiweely
-   September 25
-   3 min read

## The four layers of an Extend application

An enterprise Workday Extend application is rarely just a page. A production application spans at least four distinct structural layers, each with its own runtime behavior, configuration syntax, and failure modes:

1.  **Presentation Model Definition (PMD):** The user interface declarations, page layouts, component trees, data binding expressions, and client-side micro-scripts.
2.  **App Model Definition (AMD):** The underlying data architecture, Custom Business Objects, relationships, custom event definitions, and data types.
3.  **Orchestration for Integration (O4I):** Multi-step backend integrations running transformations, REST/SOAP outbound calls, routing logic, and error handlers.
4.  **Tenant Security and Data (WQL):** Domain Security Policies, Security Group memberships, and Workday Query Language data sources that feed information to the UI.

When an employee or manager encounters a failure in the browser, finding which of these four layers caused the breakdown is historically one of the most frustrating tasks in Workday development.

## The debugging disconnect

In a conventional developer setup, debugging requires jumping across disconnected tools, downloading multi-megabyte log files, and manually correlating timestamps:

The Multi-Layer Extend & Orchestration Stack Where errors hide vs. how kiweely traces them in a continuous loop

Layer 1: Presentation (PMD) UI Crash

**Component bindings, scripts, layouts** Browser console shows generic 500 error

Layer 2: App Model (AMD) Schema Error

**Custom business objects & fields** Attribute type mismatch or missing reference

Layer 3: Orchestration (O4I) Step Failure

**Transformation scripts, REST/SOAP calls** Step 3 rejects payload with date format error

Layer 4: Tenant Data & Security Access Denied

**Domain security & active worker queries** WQL returns empty rows due to domain permission

kiweely Diagnostic Core **Automated Root-Cause Correlation**

1.  **Automatic Log Fetch:** Queries tenant execution history via Workday APIs without downloading zip archives.
2.  **Cross-Layer Trace:** Maps the UI button click to the Orchestration trigger and downstream WQL query.
3.  **Plain-Language Verdict:** Isolates the exact step and parameter mismatch; no raw Java stack traces.
4.  **Verified One-Click Fix:** Edits the PMD or orchestration script, checks Workday compiler, and redeploys.

## The LEAK rule: clarity over stack dumps

In many development environments, an error log is a 500-line Java stack trace ending with a generic message:

Stack Trace — Orchestration Execution Log

```
com.workday.orchestration.runtime.exceptions.StepExecutionException:
  at com.workday.orchestration.steps.RestCallStep.execute(RestCallStep.java:184)
  at com.workday.orchestration.runtime.PipelineRunner.run(PipelineRunner.java:92)
Caused by: com.workday.framework.core.ValidationException: Field format invalid.
  [error_code: VALIDATION_ERROR_DATE_MISMATCH]
```

This raw output confuses functional leads and forces developers into manual archaeology. kiweely operates under the **LEAK rule**: *the assistant never passes unformatted technical stack traces directly to the person.* It reads the trace, checks the step context, cross-references tenant field configurations, and delivers a clear verdict:

> “The orchestration failed at **Step 3 (Invoke\_Worker\_REST)**. The transformation script passed the worker’s `hireDate` in `MM/DD/YYYY` format, but Workday’s REST API requires `YYYY-MM-DD`. The preceding WQL query returned an unformatted date string because the query omitted the date formatting function.”

## An end-to-end diagnosis walk-through

Consider an Extend app that submits remote work stipend requests:

1.  **The Observed Symptom:** A manager selects an employee, inputs an allowance of $500, and clicks **Submit**. The browser displays a toast: *“Submission failed. Check application logs.”*
2.  **Consultant Ask in kiweely:** *“Why did the stipend submission fail for employee 10482 in the Dev tenant?”*
3.  **Agent Inspection:**
    -   kiweely reads the latest execution record for the `Stipend_Request_Pipeline` orchestration.
    -   It verifies that Step 1 (Trigger) and Step 2 (Get\_Worker\_Eligibility) succeeded.
    -   It discovers that Step 4 (Create\_One\_Time\_Payment) failed with an HTTP 400.
    -   It inspects the employee’s compensation plan in the tenant: the worker is based in Toronto with currency `CAD`, while the orchestration hard-coded `USD` in the request body.
4.  **Proposed Solution:** kiweely proposes modifying the orchestration transformation step to dynamically pull the worker’s primary currency code from the WQL data source.
5.  **Verification:** Upon approval, the agent updates the orchestration manifest, runs Workday Extend validation, deploys the package, and initiates a test transaction to confirm the fix.

## Why this transforms team productivity

When debugging is isolated to individual surfaces, resolving an orchestration error takes multiple handoffs between functional analysts and technical developers. By correlating UI events, data models, orchestration logs, and live tenant security rules into a single continuous conversation, kiweely eliminates the guesswork.

The result is that functional consultants who understand the business logic can confidently identify, explain, and repair Extend application issues without getting lost in raw log archives.

## Read next

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

-   [November 16 ### Kiweely Roots vs Workday EIB, Studio, and Orchestrate](https://kiweely.com/blog/kiweely-roots-vs-workday-eib-studio-orchestrate)
-   [November 16 ### Orchestrate, an iPaaS, or Kiweely Roots](https://kiweely.com/blog/orchestrate-ipaas-or-kiweely-roots)
-   [November 15 ### Codex for Orchestration JSON: Catching the 25-Second Sync Trap Before Deploy](https://kiweely.com/blog/codex-orchestration-json-25-second-sync-trap)

### More guides on Orchestrate

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

-   [Global Tenant Connect in Orchestration Builder: how the tenant connection works and why it drops](https://kiweely.com/guides/workday-orchestrate-global-tenant-connect)
-   [How to generate a PDF in Workday Orchestrate and store it as an attachment](https://kiweely.com/guides/workday-orchestrate-generate-pdf-attachment)
-   [How to expose a Workday orchestration as an API an outside system can call](https://kiweely.com/guides/workday-orchestrate-expose-as-api)
-   [How to read an Excel .xlsx file in Workday Orchestrate](https://kiweely.com/guides/workday-orchestrate-excel-xlsx-files)
-   [How can a Workday orchestration tell whether it is running in production or a sandbox?](https://kiweely.com/guides/workday-orchestrate-detect-production-tenant)
-   [Reading pipe-delimited, tab-delimited, .dat and fixed-width files in Orchestrate](https://kiweely.com/guides/workday-orchestrate-delimited-fixed-width-files)
-   [Date formats and time zones in Workday Orchestrate: parse, format and convert correctly](https://kiweely.com/guides/workday-orchestrate-date-time-zone-formatting)
-   [Create Text Template in Orchestrate: XPath, JSONPath, #each loops and escaping](https://kiweely.com/guides/workday-orchestrate-create-text-template)

## Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

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

## Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.
