---
title: "Your First Workday Extend Validation Error from AI — Kiweely"
description: "What to do when Developer Agent's Extend diff fails Validate: read the code, fix the model limit, or reject the change and prompt once more."
url: https://kiweely.com/guides/first-workday-extend-validation-error-ai
---

# Your First Workday Extend Validation Error from AI

Validate checks schema, semantics, and syntax, and some of those checks do not run as you type. A generated diff can still fail. Model error codes name the limit you hit. Reject a bad diff instead of stacking repairs, and do not deploy over a red validate.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   7 min read
-   Published November 16
-   By Kiweely

A validation error on an AI-generated Extend app means App Builder refused the diff. It does not mean the tenant rejected a deploy, and it does not mean you should ask the agent to “try again” in the same breath. Validate checks schema, semantics, and syntax. Workday says some schema checks do not run while you type, so a page can look fine in the editor and still fail when you select Validate. Developer Agent can validate its own work and try to fix its own errors. That is a feature, and it is also how a single bad prompt turns into several more submissions. Your first job is to read the error and decide whether the fix is a one-line correction or a rejected diff.

Workday’s agent tutorial says the expected result is no errors, and then it says an error is possible because the agent is non-deterministic. If you are not sure how to correct it, that same page says to ask Developer Agent. Ask with the error text in the prompt. Do not ask it to regenerate the app.

## Read the failure in this order

1.  Open the validation pane. Drag it taller if the message is clipped. The message names a component. Open that component. Do not start with a fresh “build the page” prompt.
2.  If the component is one the agent just added and you have not saved, you can Reject Changes and write a tighter prompt. Reject is the right move when the page id, the task id, and the route do not agree, or when the agent invented a second business object.
3.  If the error cites a model code below, fix the model. Another prompt that adds fields will hit the same limit.
4.  Select Validate again. Save to App Hub only after it is clean. Save and Deploy is not a way to skip Validate. Save itself validates.
5.  If App Preview says it cannot preview because an existing component has a validation error, fix that existing component first. Workday says a generated page cannot be previewed while an existing component is invalid.

App Builder preserves the session as you edit. The broken file is still only a session until you save. Discard Changes throws the whole session back to the last App Hub version, irreversibly. Use that when the diff is large and wrong. Do not use it as an undo for a single field you have already mixed with hand edits you want to keep.

## Model error codes you will actually see

Workday publishes a table of model-component error codes. These are the ones that show up when a prompt asks for “a complete object” and ignores the limits. The same code number is reused for different checks. Read the description, not just `E100`.

| Code | What Workday says is wrong | What to change |
| --- | --- | --- |
| A100 | The app has too many of a model component, or more than 25 `SINGLE_INSTANCE` fields aimed at a delivered business object | Remove the extra object from this version before you promote, or stop adding Worker-shaped fields |
| B100 | More than 50 fields on the business object | Split the object only if you are willing to keep both. You cannot delete a deployed one later |
| B101 | More than 40 derived fields | Cut derived fields. Do not hide them in the page and leave them on the object |
| B102 | More than 10 `SINGLE_INSTANCE` fields on the object | Make the prompt name the ten you need |
| B110 / B111 | A field name or label matches the business object or attachment | Rename the field. `Nomination` cannot contain a field named Nomination |
| B200 | `useForDisplay` on more than one text or single-instance field | Keep one display field |
| B201 | `isReferenceId` on more than one text field | Keep one reference id field |
| B202 | App reference ID plus object name is longer than 124 characters | Shorten the object name. You cannot shorten a reference ID that already exists by editing it into a new one you used before |
| B203 | `secureByTarget` on more than one single-instance field | The nomination tutorial turns this on for the Worker field. A second field cannot also have it |
| B300 | The single-instance target object is not valid | Point at a real delivered object or an object in this app |
| E100 | A duplicate id, name, or label on a field, object, attachment, security domain, collection, business-process step, report column, or sort | The agent often duplicates a name that was already in the app. Delete the duplicate in the diff |
| E101 | An id that is not an integer from 1 to 32767 | Set an integer id. Do not leave a string |
| E102 | A name that breaks the case and character rules | Names start with a letter or number and allow letters, digits, spaces, hyphens, and colons. Workday prints both a lowercase-start rule and an uppercase-start rule under E102. Match the kind of component the rest of the file uses |
| E103 | A label that does not start with an uppercase letter or number, or uses other characters | Fix the label. Labels are not camelCase field names |
| E104 | A description over 500 characters, an expression over 1000, or a name over 100 | Shorten it. Do not ask the agent for a longer description |
| E200 | A default security domain, or a field’s security domain, that does not exist | Create the domain first, the way the nomination tutorial creates `NominationData` before the object |
| E300 | The object has no default security domain | Set one. An object must be secured |
| F100 / F101 / F102 | A field name Workday reserves | Rename it. The reserved-name list is a separate reference Workday points at from these codes |

`E105` is an invalid page route. That one is often an AMD problem: the task’s `routingPattern` or page id does not point at a real page. Open the AMD and the PMD together.

## A prompt that fixes one error

Paste the code and the limit. Do not paste “validate failed.”

```
Validate reports B102 on business object Nomination.
This object may have at most 10 SINGLE_INSTANCE fields.
Keep employeeName aimed at Worker.
Remove the extra SINGLE_INSTANCE fields you added.
Do not create a second business object.
Do not change the page routes.
```

If the agent responds by adding a new object to “move” the extra fields, Reject Changes. A new business object is a model component. Promoting it makes it permanent. B102 is a modeling problem, not a routing problem.

For a page error rather than a model code, name the three ids:

```
Validate says the create page route is invalid.
Set the task id, the page id, and the PMD name to createNomination.
Set routingPattern to /createNomination.
Do not add fields.
```

Then Validate again yourself. The overview says the agent can iterate on its own errors. You still select Validate before Save to App Hub. The agent’s claim that it fixed the file is not the validation pane.

## Failure modes

-   **You deploy anyway.** Save and Deploy validates, and a failed validation does not become a successful development test. Fix the pane first.
-   **You keep the session and prompt “fix all errors” with no code.** The agent patches around a duplicate and creates another duplicate. Quote `E100` and the duplicate name.
-   **Preview worked yesterday and Validate fails today.** An existing component is now invalid, or a schema check that does not run as you type is running now. Open the component the pane names, including ones you did not mean to touch.
-   **The code is E104 on a description the agent wrote.** Shorten the description. Do not raise a limit Workday did not publish. These numbers are the limits.
-   **You deleted a field to clear B100 on an object that already deployed.** Removal of a deployed model component is not an allowed update. If the object has not been promoted off Development, you can still change this development version. If it has deployed in a previous version, you cannot remove the field. Stop adding fields instead.

## Frequently asked questions

### Should I ask Developer Agent to fix the error or fix it myself?

If the pane names a limit in the table, fix the model or reject the extra fields. If you do not understand the message, ask Developer Agent and include the message, which is what Workday’s agent tutorial recommends. Either way, run Validate again before you save.

### Why did the editor not show the error while I typed?

Workday says App Builder does not perform some schema validations in real time. Validate is the check. Looking at highlighted JSON is not.

### Does a green “What was built” list mean Validate passed?

No. Green means the agent added a component. Yellow means it updated one. Validate is a separate action. The agent tutorial tells you to select Validate after the diff and to treat an error as possible.

### Can I preview a good new page if an old component is invalid?

Workday says no. App Preview will not show the generated page until you fix the existing component that has the validation error.

## Sources checked

-   [Create Extend Apps Using App Builder](https://developer.workday.com/documentation/xer1651695264256/CreateExtendAppsUsingAppBuilder)
-   [Reference: Model Component Error Codes](https://developer.workday.com/documentation/unm1655407599184)
-   [Developer Agent Overview](https://developer.workday.com/documentation/GUID-f1ddebc6-077a-4441-a023-3c857db88053-enHYPHENus/DeveloperAgentOverview)
-   [Build an AI Agent in Workday](https://developer.workday.com/documentation/GUID-e0052175-0a0f-407b-999b-d278ba15bab7-enHYPHENus)
-   [Concept: App Builder](https://developer.workday.com/documentation/zxh1651687589440/ConceptAppBuilder)

## Related guides

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

-   [### Workday Extend Model Components and the Weekly Update Business objects, security domains, attachments, processes, reports, and tasks are model components. Development deploys immediately. Other tenants get model changes on Friday night, and only if you promoted before Thursday. Deployed model components cannot be removed.](https://kiweely.com/guides/workday-extend-model-components-weekly-update)
-   [### The Validate and Deploy Proof Ladder for Workday Extend Preview and validate before a tenant sees anything. Save to App Hub writes a build. Deploy reaches a development tenant only. Promote one level at a time. Model components still wait for the weekly update. Orchestrations validate in Orchestration Builder.](https://kiweely.com/guides/workday-extend-validate-deploy-proof-ladder)
-   [### AMD vs PMD in Workday Extend, for Beginners In Workday Extend, the AMD declares data providers, task routes, flows, and app properties. A PMD draws one page and calls those providers. Business objects, security domains, and other model files are separate and follow the weekly update once you leave Development.](https://kiweely.com/guides/workday-extend-amd-vs-pmd-beginners)
-   [### Build Your First Workday Extend App with Developer Agent Developer Agent proposes Extend components in App Builder. You still create or accept the business object and security domain, apply the diff, validate, deploy to a development tenant, and activate the domain security policy yourself.](https://kiweely.com/guides/first-workday-extend-app-developer-agent)

### More guides on Extend apps and pages

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

-   [Security Domains for Your First Workday Extend App](https://kiweely.com/guides/first-workday-extend-app-security-domains)
-   [Is there an AI tool that can build, validate and deploy Workday Extend apps?](https://kiweely.com/guides/ai-tool-build-validate-deploy-workday-extend-apps)
-   [AI Browser Testing for Workday Extend Pages: Grids, Attachments, and BP Steps](https://kiweely.com/guides/ai-browser-testing-workday-extend-grids-attachments-bp)
-   [Workday Extend App Preview Is Not Proof the App Works in the Tenant](https://kiweely.com/guides/workday-extend-app-preview-is-not-tenant-proof)
-   [How to Map Control Fields and Related Business Objects in Workday Composite Subreports](https://kiweely.com/guides/workday-composite-report-control-fields-business-object-swap)
-   [Workday Lookup Related Value (LRV) Explained: Crossing Business Objects Without Blank Rows](https://kiweely.com/guides/workday-lookup-related-value-lrv-calculated-field)
-   [Fixing Graph API DataSourceFilter Is Inaccessible Errors and Blank processingWorker Fields When Proxying](https://kiweely.com/guides/workday-graphql-datasourcefilter-inaccessible-processingworker-proxy)
-   [Clearing Single-Instance Relationships to Null and Binding createdBy with graph:createId() in Graph API](https://kiweely.com/guides/workday-graphql-clear-single-instance-null-graph-createid)

### From the blog on Extend apps and pages

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

-   [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)
-   [FDE Playbook: First 30 Days on a Workday Extend and Studio Account](https://kiweely.com/blog/fde-playbook-first-30-days-workday-extend-studio)

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