---
title: "What does Extend PMD “failed to resolve a definition” mean?"
description: "A PMD failed to resolve error means the page names a widget, pod, script, or endpoint that is missing or mistyped. Fix the reference and redeploy."
url: https://kiweely.com/guides/workday-extend-pmd-failed-to-resolve-definition
---

# What does Extend PMD “failed to resolve a definition” mean?

Failed to resolve a definition means the PMD names a pod, script, endpoint, or widget that is missing or mistyped. Fix the reference, redeploy, and hard-refresh the page.

-   **Checked** against Workday on November 17
-   Applies to **Workday Extend Presentation Components (PMD)**
-   2 min read
-   Published November 17
-   By Kiweely

**Failed to resolve** a definition in an Extend PMD means the page names something Presentation Components cannot find when the page loads: a `podId`, an included script module, an endpoint alias, or another presentation reference that was renamed, removed, or never deployed. The app can still deploy. The page fails when it tries to resolve that name.

## What Workday resolves on a PMD

| Reference | What Workday requires |
| --- | --- |
| `pod` tag `podId` | A `.pod` file whose `podId` matches; Workday replaces the tag with the pod template before inbound fetches |
| `include` script modules | Files that exist under `presentation/scripts` and are listed in the PMD `include` array |
| `endPoints` entries | Each inbound endpoint needs at least `name`, `baseUrlType`, and `url` so the page can bind to `name` |
| Widget and binding names | Ids and endpoint names the page script and attributes actually define |

Workday’s pod reference states that during preprocessing, Presentation Components replace a `pod` tag with the pod template and substitute parameters. That replacement happens before inbound endpoints fetch data. A missing or mistyped `podId` therefore fails early as an unresolved definition, not as a quiet empty widget.

## Fix steps

1.  Copy the unresolved name from the error exactly, including capitalization.
2.  Search the app for that string. Check whether it was renamed, deleted, or only exists in a branch that never deployed.
3.  If it is a pod, open the `.pod` file and confirm `podId` matches the PMD’s `pod` tag. Pod files live in the app’s pods folder and have a 100 KB size limit.
4.  If it is a script module, confirm the filename appears in the PMD `include` array and exists under `presentation/scripts`. Pods cannot declare their own `include` or `script`; only the calling PMD loads modules.
5.  If it is an endpoint, open the PMD (and any pod that declares `endPoints`) and confirm the `name` spelling. Endpoint aliases are how the page binds data; a rename in one place without the other leaves a dangling reference.
6.  Redeploy the app, then hard-refresh the page. A cached page can keep showing the old failure after a fix.

## Prevent the next rename from breaking pages

Adopt one naming convention for widgets, pods, and endpoints. When you rename, search the whole app—including `.pod` files, which can declare their own `endPoints`. Load every page once in a non-production tenant after deploy. That catches unresolved definitions before users do.

Kiweely Vine can open the PMD and search for the unresolved name in your project when you are building or validating an Extend app on a connected machine.

## Frequently asked questions

### Why does my Extend page fail to resolve a definition after deploy?

The PMD still names a podId, endpoint, script module, or widget that is not in the deployed app. Correct the reference or restore the missing file, redeploy, and reload.

### Can a wrong podId cause failed to resolve?

Yes. Workday says a pod with the specified podId must exist in the app’s pods folder. The PMD pod tag is replaced with that template before data fetch.

### Is this the same as Failed to generate WUL from PMD?

No. Failed to resolve is a missing or mistyped reference at render time. Failed to generate WUL is a compile-time failure turning the PMD snippet into the page representation.

## Sources checked

-   [Reference: PMD Pods](https://developer.workday.com/documentation/kvp1525818876970/ReferencePMDPods)
-   [Add Pods](https://developer.workday.com/documentation/fxg1677268100051/AddPods)
-   [endPoints](https://developer.workday.com/documentation/ujr1530565661647/endPoints)
-   [include](https://developer.workday.com/documentation/hrh1604896806152/include)

## Related guides

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

-   [### Why does a PMD endpoint fail when the key is lowercase endpoints? Inbound endpoints register under endPoints (capital P). A lowercase endpoints key is ignored, so bindings fail with an unknown variable. Rename the key and reload the page.](https://kiweely.com/guides/workday-pmd-endpoint-lowercase-keys)
-   [### How do I fix “Failed to generate WUL from PMD snippet” in Extend? Failed to generate WUL from PMD means the snippet will not compile—usually a bad structure or binding shape. Shrink the widget, prove it with a literal, then match the real endpoint response.](https://kiweely.com/guides/workday-extend-failed-to-generate-wul-from-pmd)
-   [### 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)

### More guides on Extend apps and pages

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

-   [Why does an Extend edit page show Internal Server Error on submit?](https://kiweely.com/guides/workday-extend-internal-server-error-on-submit)
-   [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)
-   [Install Ready but model components missing: refresh the Extend cache](https://kiweely.com/guides/workday-extend-refresh-model-components-cache)
-   [When must I promote Extend model components before the Friday update?](https://kiweely.com/guides/workday-extend-model-component-promotion-deadlines)
-   [When should you not add Workday Extend model components?](https://kiweely.com/guides/when-not-to-add-workday-extend-model-components)
-   [Workday Extend Model Components and the Weekly Update](https://kiweely.com/guides/workday-extend-model-components-weekly-update)

### From the blog on Extend apps and pages

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

-   [How do you test a Workday Extend app end to end?](https://kiweely.com/blog/test-workday-extend-app-end-to-end)
-   [When a Workday Custom Report Is Enough vs. When You Need Prism or an Extend App](https://kiweely.com/blog/when-workday-custom-report-is-not-enough)
-   [Five Workday Extend app blueprints you can build in a free personal tenant](https://kiweely.com/blog/five-workday-extend-apps-to-build-in-open-developer-program)

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