---
title: "Why does my Extend custom validation message never display?"
description: "Custom validation text is in the API response but the PMD never shows it when responseErrorDetail or failOnStatusCodes is wrong. Fix the binding."
url: https://kiweely.com/guides/workday-extend-custom-validation-error-not-displayed
---

# Why does my Extend custom validation message never display?

Custom validation text stays hidden when responseErrorDetail is wrong or HTTP 400/403 is not in failOnStatusCodes. Map errorSummary and errors, catch those statuses, redeploy.

-   **Checked** against Workday on November 17
-   Applies to **Workday Extend edit pages with outboundData**
-   2 min read
-   Published November 17
-   By Kiweely

An Extend edit page that posts a business process or other Workday REST call can receive the custom validation text in the response and still show only a generic error. The tenant UI shows the specific message because it reads the detail payload. Your PMD only shows what `responseErrorDetail` maps—and only when Workday treats that HTTP status as a failure.

## What Workday expects on outbound errors

Workday documents a common REST error shape:

json

```
{
  "error": "An error summary.",
  "errors": [
    { "error": "An error message detail.", "code": "S21" },
    { "error": "Another error message detail.", "code": "A21" }
  ]
}
```

On an edit page, put one `responseErrorDetail` under `outboundData` for all outbound endpoints:

json

```
"responseErrorDetail": {
  "errorSummary": "<% error %>",
  "errors": "<% list:mapAttribute(errors, 'error') %>"
}
```

Workday’s `outboundData` and submitting-data samples also show `errors.map(item => { item.error })`. Both patterns pull the `error` string from each detail object. You can specify only one `responseErrorDetail` for the whole `outboundEndPoints` list.

## Status codes the page ignores by default

An outbound or validation endpoint that returns a non-2xx status is what triggers the page error UI—but only for codes Workday treats as failures. The default list includes 301, 302, 303, 307, 401, 404, 407, 408, 500, and 503. It does **not** include **400** or **403**.

If your custom validation returns HTTP 400 or 403, add those codes on the outbound endpoint:

json

```
"failOnStatusCodes": [
  { "code": 400 },
  { "code": 403 }
]
```

Without that, the detail can sit in the response while the page never runs your `responseErrorDetail` mapping the way you expect.

## Checklist when the specific message never appears

1.  Submit the same transaction in the standard Workday UI and copy the custom validation text you expect.
2.  Inspect the raw REST response from the same call the page makes. Confirm the detail string is present under `errors[].error` (or your service’s equivalent fields).
3.  Open the edit PMD `outboundData.responseErrorDetail`. Confirm `errorSummary` and `errors` bind to the real response fields.
4.  Prefer Workday’s documented list mapping (`list:mapAttribute(errors, 'error')` or the `.map` form). A mistyped list helper fails quietly and leaves you with a generic summary.
5.  Add `failOnStatusCodes` for 400 and 403 when those are the validation statuses.
6.  Redeploy and retry a known failing transaction. Do not trust a happy-path submit as proof.

## Page-level vs field-level validation

Use `onSubmit` for page-level checks before outbound calls. If `onSubmit` calls `setError` or `setWarning` on a widget, Workday returns that message and does not call outbound endpoints. Use widget `onChange` for field-level checks. Those scripted messages are separate from REST `responseErrorDetail`. If you expected a server custom validation and never saw it, confirm the outbound call actually ran.

Kiweely Vine can validate presentation components and help you read outbound error mappings in an Extend project on your machine.

## Frequently asked questions

### Why does the UI show a custom validation but my Extend app shows a generic error?

The REST response still carries the detail, but responseErrorDetail is missing, mistyped, or not catching that HTTP status. Fix the binding and failOnStatusCodes, then redeploy.

### Which binding should I use for the errors list?

Workday’s outboundData sample uses list:mapAttribute(errors, 'error') or errors.map(item => { item.error }). Map the error string field from each detail object.

### Do I need failOnStatusCodes for HTTP 400?

Yes when you want the page to treat 400 or 403 as failures. Workday’s default failure list for outbound endpoints does not include 400 or 403.

## Sources checked

-   [responseErrorDetail](https://developer.workday.com/documentation/lgo1595000847400/responseErrorDetail)
-   [outboundData](https://developer.workday.com/documentation/wyu1529974688254/outboundData)
-   [Concept: Submitting Data](https://developer.workday.com/documentation/rmd1572291186381/ConceptSubmittingData)
-   [Reference: PMD Scripting Events](https://developer.workday.com/documentation/tgy1581495452394/ReferencePMDScriptingEvents)

## Related guides

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

-   [### Why does an Extend edit page show Internal Server Error on submit? A bare Internal Server Error on submit hides an outbound endpoint failure. Read Analytics Logs, fix the payload or security, and map responseErrorDetail—including failOnStatusCodes for 400/403.](https://kiweely.com/guides/workday-extend-internal-server-error-on-submit)
-   [### Parsing Workday Business Process Custom Validation Errors Returned by REST and SOAP APIs Workday REST APIs return HTTP 400 JSON payloads containing an errors array with code, field, path, and severity (Critical or Warning), whereas Workday SOAP Web Services return HTTP 500 envelopes containing Validation\_Fault (with Xpath) or Processing\_Fault elements.](https://kiweely.com/guides/workday-business-process-validation-errors-rest-soap-responses)
-   [### onSubmit and onChange validation in Workday Extend, and why an error won’t clear An error set with setError stays until a script calls clearError. While any error remains the user can’t resubmit and onSubmit doesn’t run again, so an onSubmit check can’t clear itself. Put the clearing logic in the onChange of every widget the rule depends on.](https://kiweely.com/guides/workday-extend-onsubmit-onchange-validation)
-   [### 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)

### More guides on Extend apps and pages

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

-   [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)
-   [The Validate and Deploy Proof Ladder for Workday Extend](https://kiweely.com/guides/workday-extend-validate-deploy-proof-ladder)
-   [Promote a Workday Extend App Past Development](https://kiweely.com/guides/workday-extend-promote-past-development-beginners)

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