---
title: "Workday Extend Validation Errors: Find the Real Cause"
description: "Read a Workday Extend validation error in the right order: which check failed, the exact error code and text, the limit behind it, then the logs."
url: https://kiweely.com/guides/workday-extend-validation-errors
---

# How do I find the real cause of a Workday Extend app validation error?

First work out which check rejected the app: the App Builder Validate pane, the build log from Save to App Hub, the deploy, or the running page. Then match the code (E102, P300, B100) to Workday’s own text, fix that one cause and rerun the same check.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend model components, App Builder, App Hub**
-   7 min read
-   Published September 19
-   By Kiweely

A Workday Extend validation error comes from one of four places: the Validate pane in App Builder, the build log produced when you save to App Hub, the deployment, or the running page. Identify which one produced the message, copy the code and text exactly, look the code up in Workday’s model component error list, fix that single cause and rerun the same check.

## Which check actually rejected my Workday Extend app?

Different checks fail for different reasons, so the same app can look “broken” in four ways.

| Where you see it | What ran | Where to read more |
| --- | --- | --- |
| Validate pane in App Builder | Schema, semantic and syntax validation of the app’s code. Workday says some schema validations are not done in real time | Create Extend Apps Using App Builder |
| Build log after Save to App Hub | Save to App Hub validates and saves the code and generates a build log | App Builder build log, or `wdcli app builds logs <buildId>` |
| `wdcli app validate <appRefId>` | Validation of App Builder components only. Orchestrations are not covered | Orchestration Builder for orchestrations |
| Page error on a deployed app | The app running on a tenant | Logs tab, filtered on the common request ID |

Orchestrations have their own build logs. Workday describes them as generated when you save the orchestration to App Hub, showing how Orchestrate tried to compile it and where it hit problems. For those, continue with [why an orchestration fails](https://kiweely.com/guides/orchestrate-errors).

## In what order should I read a Workday Extend validation error?

1.  Note where the message appeared (table above). A finding from the Validate pane and a deploy failure are different events.
2.  Copy the code and the text exactly. The code (a letter and three digits, such as E102 or P300) is the key into Workday’s list.
3.  Look the code up in Reference: Model Component Error Codes. Several codes have more than one text, so match the text, not only the code.
4.  If the text mentions a limit, check the limits table before touching the design.
5.  Fix the smallest thing that removes that finding. Rerun the same check and read every finding again, because one cause can hide another.
6.  Only when validation is clean, save to App Hub, deploy and test on the tenant.

## What does error E102 mean (“Name should start with...”)?

Workday lists two texts for E102:

-   “Name should start with lowercase letter or number, and supports only alphanumeric, space, hyphen, and colon characters.”
-   “Name should start with uppercase letter or number, and supports only alphanumeric, space, hyphen, and colon characters.”

E103 is the label version: “Label should start with uppercase letter or number, and supports only alphanumeric, space, hyphen, and colon characters.” An underscore is not in the supported character list, so a name such as `time_off_request` fails. Which of the two E102 texts you get depends on the component, so read the one on your screen.

## What do E100 and E101 duplicate and id errors mean?

E100 is the duplicate family. Workday lists these texts under it, among others:

-   “Duplicate field id, name, or label.”
-   “Duplicate id, name, or label of a business object or attachment.”
-   “Duplicate id, name, or label of an action step in a business process.”
-   “Duplicate id, name, or label of a security domain.”
-   “You can’t use the same field in more than 1 column on a report.”

E101 is “The id must be an integer greater than zero and less than 32768.” E104 covers length: “Name can’t be more than 100 characters in length.”, “Description can’t be more than 500 characters in length.” and “Expression can’t be more than 1000 characters in length.”

## What do B100, B101 and B102 mean?

They are the field-count limits on a business object:

-   B100: “The number of fields exceeds the limit of 50 for your business object.”
-   B101: “The number of derived fields exceeds the limit of 40 for your business object.”
-   B102: “The number of `SINGLE_INSTANCE` fields exceeds the limit of 10 for your business object.”

Related: B202 is “The concatenation of the Reference ID of your app with the name of a business object or attachment can’t exceed 124 characters.” and D100 is “The concatenation of the name of a business object or attachment with a field ID must be unique in an app.”

## What does A100 mean (“exceeded the limit for your app”)?

A100 has two texts: “You’ve exceeded the limit for your app on the allowed number of a model component.” and “The number of `SINGLE_INSTANCE` fields where the target is a Workday-delivered business object exceeds the limit of 25 for your app.”

The per-app limits come from Workday’s Limits on Model Components page.

| Model component | Limit per app |
| --- | --- |
| Business objects | 20 |
| Security domains | 10 |
| Business processes | 5 |
| Attachments | 5 |
| Tasks | 20 |
| Reports | 10 |
| `SINGLE_INSTANCE` and `MULTI_INSTANCE` fields targeting a Workday-delivered business object | 25 |

Page, flow and endpoint limits are on separate pages and do not substitute for these.

## What do P200, P300 and P400 mean for a business process?

-   P200: “The number of action steps exceeds the limit of 5 for a business process.”
-   P300: “The approval step of a business process must include either the `APPROVE` or `DO_NOT_APPROVE` action.”
-   P400: “The `SEND_BACK` action on the approval step of a business process requires you to specify a `revisePageRoute`.” Its second text is the reverse: “You’ve specified a `revisePageRoute` on a business process without also specifying a `SEND_BACK` action on the approval step of the business process.”

E105 is the page route code: “Specify a valid page route for the” action steps, approval step, details page and revise page of a business process.

## Why do I get F101 or S101 on a field or security domain?

-   F101: “Invalid field name using a reserved field name.” Workday points to its Reserved Field Names on Business Objects list. F102 adds “Use a supported field name to prevent unexpected app behavior.”
-   F300: “Workday Extend doesn’t support `"secureByTarget": true` on `SINGLE_INSTANCE` fields that reference these target attributes.”
-   E300: “Specify at least 1 default security domain.”
-   S101: “A security domain that you enabled for page security can’t have the same name as a business object or attachment.”

## Worked example: three findings on one request-approval app

This case is built from Workday’s published rules, not captured from a customer app. A developer models a “Time Off Request” app with a business process and saves it. The Validate pane returns:

1.  E102 on the business object name `time_off_request`.
2.  P300 on the approval step, which has only a `SEND_BACK` action.
3.  P400 on the same step, because `SEND_BACK` is present with no `revisePageRoute`.

Reading in order: E102 is a naming rule, so rename the object to `Time off request` (starts with a letter, spaces allowed) and remember that anything that referenced the old name must change too. P300 says the approval step needs `APPROVE` or `DO_NOT_APPROVE`, so add one. P400 says `SEND_BACK` needs a `revisePageRoute`, so point it at a revise page that exists (E105 will complain if the route is not valid). Run Validate again. A clean pane means the model components are accepted. It does not yet mean the app works for a user, so save, deploy to a Development tenant and test with the page open. See [testing a Workday Extend app](https://kiweely.com/guides/workday-extend-testing).

## How do I debug a page error on a deployed app?

A page error shows a common request ID, for example `Internal Server Error. (id: VPS|5a438101-0f47-4cfa-a3a5-a84c13c3252b)`. Some IDs use the `WCPUI` prefix, and requests made in App Preview start with `WCPUI-APP-PREVIEW`.

1.  Copy the whole ID.
2.  In the Workday Developer Site Console, open Analytics (or select the app from Apps) and choose the Logs tab.
3.  Add a filter `wd_common_request_id is <the ID>`. Add `wd_category is console` to see PMD script logging.
4.  Read the `wd_category` values: `pageError` (page exceptions), `pageError.script` (PMD script exceptions) and `responseError` (the endpoint that failed, with HTTP status, URL and method).

If the app never reached a tenant, there is no request ID to follow. Go back to the Validate pane and the build log. For endpoint and page failures after deploy, see [Workday Extend page errors](https://kiweely.com/guides/workday-extend-pages-errors) and [deploy errors](https://kiweely.com/guides/workday-extend-deploy-errors).

## Does a clean validation mean the app works?

No. Validation reads the app’s code. Security, tenant configuration, live data and navigation only show up when the app runs. Treat validation, the build, the deployment and a role-based test as separate evidence, and record which one each result belongs to.

Kiweely Vine builds, validates and deploys Extend apps and shows Workday’s validation errors in plain terms, and treats Workday as the authority on what it accepts.

## Frequently asked questions

### Does wdcli app validate check orchestrations?

No. Workday's WDCLI reference says app validate runs validation only against App Builder components. Orchestrations are validated separately in Orchestration Builder.

### Why can an app validate cleanly and still fail later?

App Builder validation covers schema, semantic and syntax checks, and Workday notes it does not run some schema validations in real time. Deployment, security and live data are only exercised when the app runs on a tenant.

### Where do I find a page error after the app is deployed?

Copy the common request ID from the page error, open the Logs tab in Analytics or on the app, and filter wd\_common\_request\_id on that value. The pageError, pageError.script and responseError categories hold the detail.

### What is the difference between Validate and Save to App Hub?

Validate checks the code at any time without saving. Save to App Hub validates and saves the code and generates a build log. Save and Deploy also asks for a Development tenant to deploy to.

## Sources checked

-   [Reference: Model Component Error Codes](https://developer.workday.com/documentation/unm1655407599184)
-   [Create Extend Apps Using App Builder](https://developer.workday.com/documentation/xer1651695264256)
-   [Reference: Limits on Model Components](https://developer.workday.com/documentation/GUID-7d78b63a-766a-449c-839c-f7080e7e67aa)
-   [View Page Errors in the Logs](https://developer.workday.com/documentation/rlh1588897123576)
-   [Application Logs](https://developer.workday.com/documentation/hlt1558652308211)
-   [Reference: WDCLI for Extend Apps Commands](https://developer.workday.com/documentation/GUID-16d9d3f3-ba63-4022-8a84-ad78bd5189ca-enHYPHENus/ReferenceWorkdayDeveloperCLIWDCLIforExtendAppsCommands)

## Related guides

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

-   [### Workday Extend app validates but won’t deploy or promote Validation checks your source. Deploy, promote and install are separate actions against a tenant, and each fails for its own reason that validation never tests.](https://kiweely.com/guides/workday-extend-deploy-errors)
-   [### Workday Extend PMD page errors: what’s actually failing A PMD error is a break in one of three places: the endpoint call, a binding to a value that isn’t there, or a script that touches a field before checking it.](https://kiweely.com/guides/workday-extend-pages-errors)
-   [### How should I test a Workday Extend app before promoting it to production? Test in the order Workday promotes: App Preview and mock data, a Development tenant, Implementation for QA, then Sandbox with production data for acceptance. Promote to Production only after each stage has recorded evidence, because installed apps cannot be removed.](https://kiweely.com/guides/workday-extend-testing)
-   [### 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 Extend apps and pages

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

-   [Workday UI Automation Testing: Why Scripts Break and How to Automate Reliably](https://kiweely.com/guides/workday-ui-automation-testing)
-   [Why does a PMD endpoint fail when the key is lowercase endpoints?](https://kiweely.com/guides/workday-pmd-endpoint-lowercase-keys)
-   [What does Extend PMD “failed to resolve a definition” mean?](https://kiweely.com/guides/workday-extend-pmd-failed-to-resolve-definition)
-   [Why does an Extend edit page show Internal Server Error on submit?](https://kiweely.com/guides/workday-extend-internal-server-error-on-submit)
-   [How do I fix “Failed to generate WUL from PMD snippet” in Extend?](https://kiweely.com/guides/workday-extend-failed-to-generate-wul-from-pmd)
-   [Why does my Extend custom validation message never display?](https://kiweely.com/guides/workday-extend-custom-validation-error-not-displayed)
-   [How do I migrate a Workday Extend app from WCPISU to simplified ISU?](https://kiweely.com/guides/workday-migrate-wcpisu-to-simplified-isu)
-   [What is known about a December 2026 Extend model components compiler upgrade?](https://kiweely.com/guides/workday-extend-model-compiler-upgrade-2026-12)

### From the blog on Extend apps and pages

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

-   [Put a Workday Extend App in Git from Day One](https://kiweely.com/blog/workday-extend-git-from-day-one)
-   [Pairing Claude Code with a Personal Workday Extend Tenant for Portfolio Apps](https://kiweely.com/blog/claude-code-personal-workday-extend-tenant-portfolio)
-   [Claude Code Skills for Workday Extend: What Belongs in a Skill vs a Prompt](https://kiweely.com/blog/claude-code-skills-for-workday-extend)

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