---
title: "Workday Extend app validates but won't deploy or promote"
description: "Why a Workday Extend app that passes validation still fails to deploy, promote or install: tenants, security domains, credentials and timing."
url: https://kiweely.com/guides/workday-extend-deploy-errors
---

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

-   **Checked** against Workday on October 21
-   Applies to **Workday Extend**
-   9 min read
-   Published September 25
-   By Kiweely

## Deploy, promote and install are three different actions on three different objects

A clean validation, covered in [Workday Extend validation errors: find the real failure](https://kiweely.com/guides/workday-extend-validation-errors), only proves the app’s source is legal. It says nothing about whether the tenant you’re pushing to is ready to receive it. Getting an app live involves four separate actions, each against a different system, and each can fail on its own: Build, when App Hub compiles uploaded source into a versioned build; Deploy, when that build is pushed to a WCP Development tenant and labeled the Development promotion level; Promote, done from the Developer Site Console’s Apps section, which moves the latest passing build to the next promotion level — Development, Implementation, Sandbox, then Production, in that order, never skipping one; and Install, done from the **Workday Extend App Manager** worklet on the target tenant, which makes a promoted version usable there.

When someone says an app “won’t deploy,” the first thing to pin down is which of these four actions is actually the one refusing — the fix, and the system that owns it, is different for each.

## When the build itself fails, read the build log first

A failed deploy often shows only a generic “build failed”. The real list is in the build log. In App Builder, Save to App Hub validates, saves and generates one ([Create Extend Apps Using App Builder](https://developer.workday.com/documentation/xer1651695264256/CreateExtendAppsUsingAppBuilder)). With wdcli, `wdcli app builds <appRefId>` finds the build and `wdcli app builds logs <buildId>` prints it ([WDCLI commands](https://developer.workday.com/documentation/GUID-16d9d3f3-ba63-4022-8a84-ad78bd5189ca-enHYPHENus/ReferenceWorkdayDeveloperCLIWDCLIforExtendAppsCommands)). The build reports every validation error together, so fix them in one pass.

Common model component codes, from Workday’s [Model Component Error Codes](https://developer.workday.com/documentation/unm1655407599184/ReferenceModelComponentErrorCodes):

| Code | Meaning |
| --- | --- |
| B100 | More than 50 fields in a business object |
| B101 | More than 40 derived fields |
| B102 | More than 10 `SINGLE_INSTANCE` fields |
| B110 / B111 | A field has the same name or label as its business object or attachment |
| B200 | `useForDisplay` is allowed on only 1 `TEXT` or `SINGLE_INSTANCE` field |
| B201 | `isReferenceId` is allowed on only 1 `TEXT` field |
| B202 | App reference ID + object name is longer than 124 characters |
| B203 | `secureByTarget` is allowed on only 1 `SINGLE_INSTANCE` field |
| B300 | Invalid target object on a `SINGLE_INSTANCE` field |

Validated locally but the deploy still failed? `wdcli app validate` doesn’t check orchestrations. Validate them in Orchestration Builder.

## What has to exist before the first non-Development install

Before you can install a Workday Extend app on any tenant beyond Development, Workday requires: the **Workday Extend App Manager** worklet added to that tenant’s Workday Home page; every *Workday Extend* security domain in the System functional area enabled, with a security policy created for each one; and membership in a security group with Modify access on the *Manage: App Manager* domain, since that’s what App Hub checks before it lets you deploy at all.

If the Workday Extend App Manager worklet shows your app on its **Needs Attention** tab on the Development tenant, redeploy it there first. Nothing beyond Development will accept a build that Workday still considers unresolved on its own home tenant.

## The target tenant may not be enabled for Workday Extend at all

When you purchase Workday Extend, Workday automatically enables your Implementation, Production, Sandbox and Sandbox Preview tenants for it. The setting itself sits on the Manage Workday Cloud Platform task, secured to the Security Administration domain; your Named Support Contact enables it, and Workday notes that the same setting has to be enabled on that task in your Sandbox and Production tenants.

Before assuming a promote or install failure is the app’s fault, run the **Domain Security Policies for Functional Areas** report against the System functional area on the target tenant and confirm the *Workday Extend* domain has active security policies there. An app that promotes cleanly through the Developer Site can still have nowhere to install if the receiving tenant was never enabled.

## A security domain that isn’t enabled, or isn’t activated, blocks the deploy at two different levels

There are two separate sets of security domains involved, and both have to be current on the target tenant. At the platform level, *Custom Business Process*, *Custom Task*, *Manage: App Manager* and *WQL for Workday Extend* each need their own security policy, created through **Create Security Policy for Domain** and pushed live with **Activate Pending Security Policy Changes**. A policy that’s saved but never activated behaves, from the app’s point of view, as if it doesn’t exist.

At the app level, a security domain authored inside App Builder defaults to the label **My Security Domain** until you rename it, and only takes effect once the corresponding flag is set — `enabledForPageSecurity` for a page, `enabledForOrchestrationSecurity` for an orchestration. Each of those app-defined domains still needs its own security policy configured, and activated, separately on every tenant the app is installed to; a policy that exists in Sandbox doesn’t travel with the app when it promotes to Production.

## Orchestration credentials belong to the tenant, not to the app version

An orchestration’s authentication — API Key, Basic Authentication, OAuth, or Integration System User — is configured as a named credential, and that credential is tenant-specific. A credential created while developing on the Development tenant does not exist on Implementation, Sandbox, or Production; it has to be recreated on each tenant the app is promoted to, under the same credential name the app’s source expects.

Sandbox and Sandbox Preview are a common trap: even though they can share the same promoted app version, each needs its own refresh tokens created separately on the external client credential store. Create a business object in Sandbox Preview without a matching refresh token there, and requests against it return HTTP 500 even though the identical request works on Sandbox. For the specific error text these credential problems produce at runtime, see [Workday Orchestrate errors and what they mean](https://kiweely.com/guides/orchestrate-errors).

## Model components move on Workday’s weekly schedule, not on your click

An app’s model components — its business objects, business processes and the security domains defined on them — only reach a tenant during Workday’s Weekly Service Update, not immediately when you promote. Promote before your region and data center’s weekly deadline (Thursday, in most cases) and the update lands the following Friday night; promote after it, and the update waits a full week. Until that update runs, you can’t install the app on that tenant at all, no matter how many times you click Install.

If a colleague reports that an already-installed app is missing model components, that’s usually a caching issue rather than a failed deploy: ask your account’s Developer Support Contact whether the **Refresh Extend Model Components Cache** task needs to run before you go looking for a defect in the app itself.

## Promotion only moves one step at a time, and it replaces what’s already there

You can promote an app from Development to Implementation, Implementation to Sandbox, or Sandbox to Production — never further in one step, and never out of order. Each promotion replaces the version of the app currently sitting at that level; there’s no side-by-side versioning once you’re past Development. Promoting to Production specifically requires reading a checklist on the Developer Site and confirming **My app meets these criteria** before Workday lets the promotion through.

Once an app is installed on an Implementation, Sandbox, or Production tenant, it can’t simply be removed from that tenant — only retired. Plan the first install on a non-Development tenant accordingly; it’s a one-way door for that tenant.

## A model change rejected at promotion is a lifecycle rule, not a syntax error

Once an app has been promoted past Development, Workday only allows specific changes to its model components. On a business object, you can still change a label, a name, or a security domain assignment, or flip a handful of named attributes — but not, for example, change a field’s underlying type. Business processes, tasks and reports have their own, shorter lists of what’s still changeable after promotion. A field or property that isn’t on the allowed list is rejected at promote time, even though the exact same source validates and builds cleanly as a standalone change on Development.

When a promotion fails only on a later version of an app that’s already live somewhere beyond Development, compare the specific model property you changed against what’s actually allowed after promotion, rather than re-reading the component’s validation rules again — validation already passed; this is a different check.

## A Sandbox refresh can silently uninstall your app

Sandbox tenants are refreshed regularly from Production data, and Implementation tenants get refreshed too. If a Sandbox tenant refreshes before you’ve installed your latest version on Production, or an Implementation tenant refreshes from a source tenant where the app was never installed, the app has to be reinstalled on that tenant from scratch — and reconfigured: business process definitions, business process security policies, custom tasks and domain security policies all have to be recreated, not just the app itself reinstalled.

If a deploy that worked last week suddenly fails, or the app’s configuration has reverted, check whether the tenant was refreshed in between before debugging the app. See [what a Sandbox refresh actually resets](https://kiweely.com/guides/workday-sandbox-refresh) for the refresh cadence and what it does and doesn’t preserve.

## Confirm the fix at the same tenant, not just on the Developer Site

A promotion or install that finally goes through on the Developer Site still isn’t proof the app works for its users on that tenant — security domain activation, model component timing and installed configuration all sit outside what the Console shows you. Use [the Workday Extend testing method](https://kiweely.com/guides/workday-extend-testing) to confirm the deployed app behaves correctly for the intended roles once it’s actually installed.

kiweely builds, validates and deploys Extend apps against a client’s own tenant, one step at a time, so it hits these same tenant-level checks — a missing security policy, an uncreated credential, a tenant that isn’t Extend-enabled — directly rather than guessing from the source alone. kiweely reads the build status and Workday’s own build log for a failed Extend build, or Studio’s builder errors and validation markers for a Studio integration. It fixes the source, re-validates and redeploys to your Development tenant once you approve. Workday, not kiweely, decides whether it passed. Results appear in kiweely’s reply in the conversation. On Mac, from 1.0.19, first-time Studio setup is one step. Each project’s Monitor keeps the issue’s history. It runs on Mac and on Windows from Microsoft Store; Vine Free is free for one person, with no card and no trial.

For component-level validation or build failures that happen before any of this, go back to [Workday Extend validation errors: find the real failure](https://kiweely.com/guides/workday-extend-validation-errors).

## FAQ

**Where do I find the real error for a failed Extend deploy?** In the build log: App Builder generates one when you save to App Hub, and `wdcli app builds logs <buildId>` prints it.

**What does error B200 mean?** `useForDisplay` is set on more than one field. Workday allows it on only one `TEXT` or `SINGLE_INSTANCE` field per business object.

**Why did my app validate but still fail to deploy?** `wdcli app validate` only checks App Builder components, so orchestrations need separate validation. Deploy and install also depend on the target tenant (security policies, credentials, Extend enablement), which validation never checks.

**Why is my promotion waiting?** Model components reach a tenant only in Workday’s Weekly Service Update, so a promotion after your region’s weekly deadline waits a week.

**Can kiweely fix a failed build for me?** Yes. kiweely reads the build status and Workday’s own build log for a failed Extend build, or Studio’s builder errors and validation markers for a Studio integration. It fixes the source, re-validates and redeploys to your Development tenant once you approve. Workday, not kiweely, decides whether it passed.

## Sources checked

-   [Concept: Workday Extend App Lifecycle](https://developer.workday.com/documentation/cjw1620248412279)
-   [Deploy Extend Apps: Before You Begin](https://developer.workday.com/documentation/zlx1623192834267)
-   [Promote Extend Apps Through the Lifecycle](https://developer.workday.com/documentation/ujq1579478936974)
-   [Install Extend Apps on Tenants](https://developer.workday.com/documentation/ugq1579118511143)
-   [Concept: App Hub](https://developer.workday.com/documentation/vls1578430279610)
-   [Enable Non-Development Tenants for Workday Extend](https://developer.workday.com/documentation/tsm1574197307343)
-   [Add Security Domains](https://developer.workday.com/documentation/azx1677268395516)
-   [Reference: Allowed Updates After Extend App Promotion](https://developer.workday.com/documentation/haf1635898070118)
-   [Reference: Promotion Deadlines for Extend Apps with Model Components](https://developer.workday.com/documentation/giw1660842903762)
-   [Reference: Model Component Error Codes](https://developer.workday.com/documentation/unm1655407599184/ReferenceModelComponentErrorCodes)
-   [Reference: WDCLI for Extend Apps Commands](https://developer.workday.com/documentation/GUID-16d9d3f3-ba63-4022-8a84-ad78bd5189ca-enHYPHENus/ReferenceWorkdayDeveloperCLIWDCLIforExtendAppsCommands)
-   [Create Extend Apps Using App Builder](https://developer.workday.com/documentation/xer1651695264256/CreateExtendAppsUsingAppBuilder)

## Related guides

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

-   [### 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 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.](https://kiweely.com/guides/workday-extend-validation-errors)
-   [### 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 Extend PMD page errors: what’s actually failing](https://kiweely.com/guides/workday-extend-pages-errors)
-   [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)

### From the blog on Extend apps and pages

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

-   [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)
-   [Claude Code vs Codex for Workday Extend: What Each Can Reach Today](https://kiweely.com/blog/claude-code-vs-codex-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.
