---
title: "Why does an Extend edit page show Internal Server Error on…"
description: "A bare Internal Server Error on submit hides an outbound endpoint failure. Read Extend logs, fix the payload or failOnStatusCodes, then resubmit."
url: https://kiweely.com/guides/workday-extend-internal-server-error-on-submit
---

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

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

An Extend edit page that shows only **Internal Server Error** after OK has already compiled. The failure is on an outbound endpoint (or a validation endpoint) during submit. The page suppressed the detail; the Developer Site log still has it.

## What happens on OK

Workday’s submitting-data and `outboundData` docs say that when the user clicks OK, Presentation Components submit the outbound endpoints with bodies built from widget values. One shared `responseErrorDetail` covers all outbound endpoints. Non-2xx responses are supposed to drive the page error UI—when the status is treated as a failure and the bindings match the response.

Default failure statuses include 401, 404, 408, **500**, and 503, among others. They do **not** include 400 or 403 unless you list them in `failOnStatusCodes`.

## Find the real failure

1.  Open the app on the Developer Site Console. Go to **Analytics**, then **Logs**.
2.  Submit the edit page again and wait for the log line for that action.
3.  Read the status and message on the failing outbound call. A 4xx points at payload or security; a 5xx points at the service behind the endpoint.
4.  If the page has multiple outbound endpoints, temporarily exclude or remove the newest one and resubmit. When the page succeeds again, the fault is in that call’s body or permissions.
5.  Compare the JSON `onSend` builds to what the target API expects—reference objects vs plain strings, required fields left empty, wrong ids.
6.  Confirm the authentication scheme on the endpoint (SSO or ISU) can access every object that call touches.

## Make the next failure readable

Add `responseErrorDetail` if it is missing:

json

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

For validation statuses:

json

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

Use `onSubmit` for page-level checks that should block outbound calls before they run. Build multi-endpoint submit sequences one call at a time, checking Logs after each addition.

Kiweely Vine can validate Extend pages and help you inspect outbound mappings in a project on your machine. The Developer Site log remains the authority for a live Internal Server Error.

## Frequently asked questions

### Where is the real error when the page only says Internal Server Error?

In the Extend app’s Analytics Logs on the Developer Site. Resubmit once and read the log line for the outbound call.

### Why did submit break after I added a second outbound endpoint?

outboundData can call several endpoints on OK. The new call’s payload or permissions failed while the first call still succeeded alone.

### Will responseErrorDetail show HTTP 500 details?

500 is in Workday’s default failure status list. Map errorSummary and errors to the response fields. For 400 and 403, add failOnStatusCodes.

## Sources checked

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

## Related guides

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

-   [### 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.](https://kiweely.com/guides/workday-extend-custom-validation-error-not-displayed)
-   [### 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 fix “Failed to generate WUL from PMD snippet” in Extend?](https://kiweely.com/guides/workday-extend-failed-to-generate-wul-from-pmd)
-   [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)

### From the blog on Extend apps and pages

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

-   [How to Put Custom Employee Screens in Front of Workday Without a Workday Extend License](https://kiweely.com/blog/custom-employee-ui-for-workday-without-workday-extend)
-   [Workday Extend vs. Power Apps and ServiceNow App Engine: where to build a Workday app](https://kiweely.com/blog/workday-extend-vs-power-apps-servicenow-app-engine)
-   [What can you change in a Workday Extend app after its model components deploy?](https://kiweely.com/blog/workday-extend-model-components-first-deploy)

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