---
title: "How do I fix “WCPISU is not configured” on an Extend…"
description: "WCPISU is not configured means the ISU is missing from App Manager or has no API client. Assign the ISU, create the client, rerun."
url: https://kiweely.com/guides/workday-extend-wcpisu-not-configured-error
---

# How do I fix “WCPISU is not configured” on an Extend orchestration?

WCPISU is not configured means the ISU is missing from App Manager or has no API client. Assign the ISU, create the client, then finish orchestration credentials. Prefer simplified ISU for new apps.

-   **Checked** against Workday on November 17
-   Applies to **Workday Extend orchestrations using ISU authentication**
-   2 min read
-   Published November 17
-   By Kiweely

The orchestration error **WCPISU with username ‘<ISU\_NAME>’ is not configured in this tenant for appRefId ‘<APP\_REF\_ID>’. You can use App Manager to configure it.** means the credential names an Integration System User that this app cannot use yet in this tenant. Assign the ISU and create its API client before you debug the business API step.

## What “configured” means in App Manager

Workday’s setup path for ISU authentication is:

1.  Create Integration System Users for apps (with the right security group and domains).
2.  **Assign Integration System Users to an App** in App Manager.
3.  Click **Create API Client** on the ISU row.
4.  Create orchestration credentials (and, for pages, configure ISU authentication in presentation components).

You may add multiple ISUs to one app, but **an ISU can be associated with only one app**. The Add Integration System User button requires the **WCP Integration System User Security** domain.

## Fix steps

1.  Compare the username in the orchestration credential to the ISU in the tenant. Spelling must match exactly.
2.  In App Manager, open the app → Configure → Integration System Users. Add the ISU if it is missing.
3.  On the ISU row, click **Create API Client** if no client id is shown. Confirm and OK. The generated client name follows `App: Env: Tenant: ISU: …`.
4.  If Create API Client returns **409**, delete the leftover client for that ISU on the Developer Site Console, then create again (see the 409 guide).
5.  Complete orchestration credentials for the simplified ISU (or legacy WCPISU setup only if this is an existing app still on that scheme).
6.  Rerun the orchestration in this tenant.

## Legacy WCPISU versus simplified ISU

Workday’s ISU authentication concept states that **`WCPISU` is a legacy mechanism**. New apps must use simplified **`ISU`**. Orchestration Builder credentials use simplified ISU. Existing apps can keep WCPISU but Workday strongly recommends migration. You cannot configure simplified ISU with the old API clients that were used for legacy WCPISU.

For legacy WCPISU presentation setups, Workday still documents External Client CredStore, `scheme: "WCPISU"` in the SMD, and `authType` on each `endPoints` entry. Prefer migration over extending that pattern.

Repeat ISU assignment and API client creation in **every tenant** you promote to. App Manager configuration does not travel automatically with the app binary alone.

Kiweely Vine can help you follow ISU setup against Workday’s steps on a connected developer tenant. App Manager and Developer Site Console actions remain yours to confirm.

## Frequently asked questions

### What does the WCPISU is not configured message mean?

The orchestration names an ISU that is not assigned to this app in this tenant, or the ISU row has no API client yet. Configure it in App Manager.

### Should new apps still use the WCPISU scheme?

No. Workday recommends simplified ISU authentication. Existing apps may keep legacy WCPISU; new apps must use ISU.

### Why is my ISU missing from the App Manager picker?

An ISU can be associated with only one app. If another app already owns it, it will not appear as unassigned.

## Sources checked

-   [Concept: ISU Authentication](https://developer.workday.com/documentation/GUID-cb3e0fcd-bb97-4005-8d10-3a02e88dab71-enHYPHENus/ConceptISUAuthentication)
-   [Assign Integration System Users to an App](https://developer.workday.com/documentation/GUID-72d57df4-c4ec-4825-a6e8-fdd596cf930e/AssignIntegrationSystemUserstoanApp)
-   [Steps: Set Up ISU Authentication for Apps](https://developer.workday.com/documentation/GUID-3277fec3-24c9-41da-9840-c61b41033f28-enHYPHENus/StepsSetUpISUAuthenticationforApps)
-   [Steps: Set Up WCP Integration System User Authentication (WCPISU)](https://developer.workday.com/documentation/sha1524170857897/StepsSetUpWCPIntegrationSystemUserAuthenticationWCPISU)

## Related guides

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

-   [### Why does WQL return 403 permission denied S22 for an ISU? WQL 403 with S22 means the ISU lacks permission—usually the Workday Query Language domain or a data-source domain. Grant access on the ISSG, activate security, and rerun as the ISU.](https://kiweely.com/guides/workday-wql-403-s22-as-isu)
-   [### Why does Create WCP API Client return 409 for an ISU? Create API Client 409 means a leftover Developer Site client still uses that ISU name. Delete the stale client (Company Administrator), create again from App Manager, and authorize the tenant.](https://kiweely.com/guides/workday-create-api-client-409-isu-already-has-client)
-   [### WCPISU explained: the legacy Workday Cloud Platform integration system user in Extend WCPISU is Extend’s legacy way for a page endpoint to run as an integration system user: you get a refresh token for the ISU, store it with Create External Client CredStore, and point the SMD at it by appId and tokenHolder. New apps must use the simplified ISU scheme instead.](https://kiweely.com/guides/workday-wcpisu-explained)
-   [### Workday ISU or API client 401, invalid\_client, invalid\_grant These errors usually blame the token, but the real cause is the ISU’s own account, its security group’s activation, or the wrong client task — not a corrupted credential.](https://kiweely.com/guides/workday-isu-authentication-errors)

### More guides on Orchestrate

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

-   [When to use Workday Document Transformation instead of Orchestrate or Studio](https://kiweely.com/guides/workday-document-transformation-connector-when)
-   [Start with a Workday packaged connector before custom Studio](https://kiweely.com/guides/workday-packaged-connector-before-studio)
-   [Three cases where Workday still wants Studio](https://kiweely.com/guides/workday-studio-three-cases-keep-studio)
-   [Orchestrate is not a bulk-load replacement for Workday EIB or Studio](https://kiweely.com/guides/workday-orchestrate-not-a-bulk-load-replacement)
-   [Why Workday Orchestrate Trigger Integration will not launch an EIB](https://kiweely.com/guides/workday-trigger-integration-cannot-launch-eib)
-   [The 25-Second Synchronous Orchestrate Trap](https://kiweely.com/guides/workday-orchestrate-25-second-sync-trap)
-   [What is the best AI tool for building and testing Workday Studio integrations and Orchestrations?](https://kiweely.com/guides/ai-tools-for-workday-studio-and-orchestrations)
-   [How are API calls from Workday Orchestrate and Extend apps limited and counted, and can I set my own rate limit?](https://kiweely.com/guides/workday-orchestrate-api-usage-limits-quota)

### From the blog on Orchestrate

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

-   [How Kiweely Vine designs, builds, deploys, tests and monitors a Workday Orchestration for Integration](https://kiweely.com/blog/workday-orchestration-for-integration-with-kiweely)
-   [Why Workday Studio Remains Essential in an Orchestrate World](https://kiweely.com/blog/why-workday-studio-still-matters-with-orchestrate)
-   [Debugging Workday Extend apps and orchestrations in kiweely](https://kiweely.com/blog/debugging-workday-extend-apps-orchestrations-kiweely)

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