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
- 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.
- 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.
- If the error cites a model code below, fix the model. Another prompt that adds fields will hit the same limit.
- 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.
- 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 |
|---|---|---|
| CodeA100 | What Workday says is wrongThe app has too many of a model component, or more than 25 SINGLE_INSTANCE fields aimed at a delivered business object |
What to changeRemove the extra object from this version before you promote, or stop adding Worker-shaped fields |
| CodeB100 | What Workday says is wrongMore than 50 fields on the business object | What to changeSplit the object only if you are willing to keep both. You cannot delete a deployed one later |
| CodeB101 | What Workday says is wrongMore than 40 derived fields | What to changeCut derived fields. Do not hide them in the page and leave them on the object |
| CodeB102 | What Workday says is wrongMore than 10 SINGLE_INSTANCE fields on the object |
What to changeMake the prompt name the ten you need |
| CodeB110 / B111 | What Workday says is wrongA field name or label matches the business object or attachment | What to changeRename the field. Nomination cannot contain a field named Nomination |
| CodeB200 | What Workday says is wronguseForDisplay on more than one text or single-instance field |
What to changeKeep one display field |
| CodeB201 | What Workday says is wrongisReferenceId on more than one text field |
What to changeKeep one reference id field |
| CodeB202 | What Workday says is wrongApp reference ID plus object name is longer than 124 characters | What to changeShorten the object name. You cannot shorten a reference ID that already exists by editing it into a new one you used before |
| CodeB203 | What Workday says is wrongsecureByTarget on more than one single-instance field |
What to changeThe nomination tutorial turns this on for the Worker field. A second field cannot also have it |
| CodeB300 | What Workday says is wrongThe single-instance target object is not valid | What to changePoint at a real delivered object or an object in this app |
| CodeE100 | What Workday says is wrongA duplicate id, name, or label on a field, object, attachment, security domain, collection, business-process step, report column, or sort | What to changeThe agent often duplicates a name that was already in the app. Delete the duplicate in the diff |
| CodeE101 | What Workday says is wrongAn id that is not an integer from 1 to 32767 | What to changeSet an integer id. Do not leave a string |
| CodeE102 | What Workday says is wrongA name that breaks the case and character rules | What to changeNames 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 |
| CodeE103 | What Workday says is wrongA label that does not start with an uppercase letter or number, or uses other characters | What to changeFix the label. Labels are not camelCase field names |
| CodeE104 | What Workday says is wrongA description over 500 characters, an expression over 1000, or a name over 100 | What to changeShorten it. Do not ask the agent for a longer description |
| CodeE200 | What Workday says is wrongA default security domain, or a field’s security domain, that does not exist | What to changeCreate the domain first, the way the nomination tutorial creates NominationData before the object |
| CodeE300 | What Workday says is wrongThe object has no default security domain | What to changeSet one. An object must be secured |
| CodeF100 / F101 / F102 | What Workday says is wrongA field name Workday reserves | What to changeRename 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
E100and 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.