---
title: "Install Ready but model components missing: refresh the…"
description: "If an Extend app is installed but model components are missing at Configure, ask Developer Support about Refresh Extend Model Components Cache."
url: https://kiweely.com/guides/workday-extend-refresh-model-components-cache
---

# Install Ready but model components missing: refresh the Extend cache

App Manager can show an app as installed while model components are still unavailable. Workday’s install guide says to contact your Developer Support Contact about the Refresh Extend Model Components Cache task. First confirm the weekly update already ran.

-   **Checked** against Workday on November 17
-   Applies to **Workday Extend App Manager on Implementation, Sandbox, and Production**
-   3 min read
-   Published November 17
-   By Kiweely

An Extend app can sit on App Manager’s install path while its model components are still missing when you open Configure. Workday’s install guide covers that exact note: if the model components are not available when you attempt to configure the app, contact your account’s Developer Support Contact to determine whether you need to run the **Refresh Extend Model Components Cache** task.

Do not treat that task as a substitute for the Weekly Service Update. Model components must deploy with Friday’s update before they are installable on Implementation, Sandbox, or Production.

## What “Ready” and “Installed” actually mean

Workday’s install steps are short:

1.  Sign in to the tenant.
2.  On the **Ready to Install** tab in App Manager, select the app and click **Install**.
3.  Confirm. Once installed on a non-Development tenant, you cannot remove the app from that tenant.
4.  On the **Installed** tab, select the app and click **Configure**.

You only need to install once per tenant. When you update the app later, you do not reinstall.

The gap this guide covers appears at step 4: Configure opens, but the model components the app expects are not available yet.

## Diagnose before you ask for a cache refresh

| Check | Why it matters |
| --- | --- |
| Was the app promoted before your region’s Thursday Pacific deadline? | Late promotions schedule model components for Friday night one week later. |
| Has the Weekly Service Update for that promotion already completed? | You cannot install (and should not expect Configure to expose) model components before they deploy with that update. |
| Are you looking at the correct tenant type for the promotion level? | Implementation, Sandbox, and Production each need their own install. |
| Did you just promote and are waiting only a few minutes? | Workday says Implementation may take up to 1 minute, and Sandbox or Production up to 15 minutes, to update the cached app. That is not the Friday model deploy. |
| Was the Implementation or Sandbox tenant refreshed from a tenant that never had the app? | Workday says you must reinstall, and you must recreate business process definitions, business process security policies, custom tasks, and domain security policies. |

Only after those checks still leave Configure without model components should you involve Developer Support about **Refresh Extend Model Components Cache**.

## Prerequisites that block install entirely

Before App Manager can do useful work, Workday requires:

-   The **Workday Extend App Manager** worklet on the Home page.
-   All Workday Extend security domains in the System functional area enabled, with security policies that grant **Modify** access.

If those are missing, fix them first. A cache refresh will not replace domain setup.

## First Production go-live timing

For a first customer go-live, Workday says to promote the app to Production one week before Workday creates Production from Gold. Otherwise the app is not available to install on Production until you promote it to Production. A missing Production install in that window is a promotion-timing problem, not a cache problem.

## What to tell Developer Support

Keep the ticket factual:

1.  App name and promotion level.
2.  Tenant type and whether Friday’s Weekly Service Update for that promotion has completed.
3.  Exact symptom: Installed, Configure attempted, model components not available.
4.  Whether a tenant refresh recently forced a reinstall.
5.  Ask whether **Refresh Extend Model Components Cache** is required for this account.

Workday’s public install page does not publish a self-serve runbook for that task beyond contacting Developer Support. Do not invent steps that are not on the page.

## Failure modes

-   **Refreshing the cache on Thursday for a Friday-queued object.** The weekly update has not deployed the model yet. Wait for Friday night after an on-time promotion.
-   **Reinstalling hoping to force model components.** Workday installs once. Reinstall is for refresh scenarios that wiped the install, not for skipping Friday.
-   **Confusing app-cache wait with model deploy.** Fifteen minutes can explain a missing promoted build on Sandbox or Production. It does not deploy new model components early.
-   **Skipping security domain activation after the model finally appears.** Domains in the app are not the same as activated policy in the tenant.

## Frequently asked questions

### Is Refresh Extend Model Components Cache the first step?

No. First confirm promotion timing and that the Weekly Service Update for model components has completed. Workday documents the refresh task as something to discuss with Developer Support when configure still cannot see the model.

### Do I reinstall the app to pick up a later version?

No. Workday says you install once per tenant. Updates do not require reinstall.

### How long can the promoted app cache take?

Up to 1 minute on Implementation, and up to 15 minutes on Sandbox and Production. That cache wait is separate from Friday's model-component deploy.

## Sources checked

-   [Install Extend Apps on Tenants](https://developer.workday.com/documentation/ugq1579118511143/InstallExtendAppsonTenants)
-   [Concept: Extend Apps with Model Components](https://developer.workday.com/documentation/svf1623189172850/ConceptExtendAppswithModelComponents)
-   [Promote Extend Apps Through the Lifecycle](https://developer.workday.com/documentation/ujq1579478936974/PromoteExtendAppsThroughtheLifecycle)
-   [Reference: Promotion Deadlines for Extend Apps with Model Components](https://developer.workday.com/documentation/giw1660842903762/ReferencePromotionDeadlinesforExtendAppswithModelComponents)

## Related guides

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

-   [### When must I promote Extend model components before the Friday update? Promote before your region’s Thursday Pacific deadline and new or updated model components deploy Friday night. Miss it and Workday schedules them for Friday night one week later. EU and four Asia-Pacific US data centers cut off Thursday morning Pacific.](https://kiweely.com/guides/workday-extend-model-component-promotion-deadlines)
-   [### Workday Extend Model Components and the Weekly Update Business objects, security domains, attachments, processes, reports, and tasks are model components. Development deploys immediately. Other tenants get model changes on Friday night, and only if you promoted before Thursday. Deployed model components cannot be removed.](https://kiweely.com/guides/workday-extend-model-components-weekly-update)
-   [### Promote a Workday Extend App Past Development Deploy and test on a development tenant, then promote only to the next level. Implementation can take a minute to refresh. Sandbox and Production can take 15 minutes. Model components still wait for Friday if you made the Thursday deadline. Install once per tenant.](https://kiweely.com/guides/workday-extend-promote-past-development-beginners)

### More guides on Extend apps and pages

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

-   [When should you not add Workday Extend model components?](https://kiweely.com/guides/when-not-to-add-workday-extend-model-components)
-   [The Validate and Deploy Proof Ladder for Workday Extend](https://kiweely.com/guides/workday-extend-validate-deploy-proof-ladder)
-   [Use the Workday Extend App Catalog as an AI Jump Start](https://kiweely.com/guides/workday-extend-app-catalog-ai-jump-start)
-   [AMD vs PMD in Workday Extend, for Beginners](https://kiweely.com/guides/workday-extend-amd-vs-pmd-beginners)
-   [Your First Workday Extend Validation Error from AI](https://kiweely.com/guides/first-workday-extend-validation-error-ai)
-   [Security Domains for Your First Workday Extend App](https://kiweely.com/guides/first-workday-extend-app-security-domains)
-   [Is there an AI tool that can build, validate and deploy Workday Extend apps?](https://kiweely.com/guides/ai-tool-build-validate-deploy-workday-extend-apps)
-   [AI Browser Testing for Workday Extend Pages: Grids, Attachments, and BP Steps](https://kiweely.com/guides/ai-browser-testing-workday-extend-grids-attachments-bp)

### From the blog on Extend apps and pages

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

-   [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)
-   [From Business Brief to Tested Workday Extend App: Why Zero Validation Errors Is Not Proof](https://kiweely.com/blog/why-workday-extend-validation-is-not-testing)

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