DX Custom Component Working Locally but "Component Not Found" After Publishing to Pega

User Experience
1

Hi Team,

I have developed a custom DX component for a Constellation application.

Scenario

  • Created a custom DX component using the DX Components framework.

  • Component works perfectly when running locally using the development server.

  • Successfully built and published the component package.

  • Imported/published the component into Pega.

  • During runtime, Pega is unable to load the component and throws a Component Not Found error.

  • image
    image1066Ă—361 21.2 KB

What I Have Verified

  1. Component works correctly in local development.

  2. Build completed successfully without errors.

  3. Component package was published and imported into Pega.

  4. Rule references in the View configuration appear correct.

  5. Browser cache cleared and application reloaded.

Questions

  1. What could cause a DX component to work locally but not be found after deployment in Pega?

  2. Are there any additional steps required after publishing the component package?

  3. How can I verify that the component registration was successful in Pega?

  4. Is there a way to check whether the component metadata is available to the Constellation runtime?

  5. Are there any known issues related to component naming, namespace configuration, or deployment package versions?

Environment

  • Pega Version: [Please specify]

  • Constellation Version: [Please specify]

  • DX Component Framework Version: [Please specify]

Any guidance or troubleshooting steps would be greatly appreciated.

Thanks

Vijay Ganesam

2

A few resources that might help:

  1. Extending Constellation: A Deep Dive into Constellation DX Components | Pega
  2. Extending Constellation UI: DX Component Full Lifecycle | Pega

It could be multiple things, a bit hard to tell from your description exactly which.

  • Ruleset Misalignment in the Application Stack
  • Desynchronization of UI Assets (Pega '24.2 and Earlier)
  • Browser Cache and Unsaved Application Rules
  • Operator Security Settings

Your version information didn’t post correctly, that may help as '24 and '25 have some different details.

3

Hi @MarcCheong

Thank you for your response.

We are currently using Pega Platform 25.1.

To provide additional context, I developed a custom DX Component named _Alamaticz_DarkMode. The component works as expected in my local DX Component development environment. However, after publishing and deploying it to the Pega application, I am encountering the following runtime error:

PyComponent_Not_Found
Component Not Found - _Alamaticz_DarkMode
The resource cannot be found.

The component is referenced correctly in the view configuration, and the deployment completed without any obvious errors.

Could you please advise on any Pega 25.1-specific checks or configuration areas that I should verify, such as component registration, deployment packaging, static content availability, or Constellation DX Component configuration?

Thank you for your guidance and support.

4

Go to Library>DX Components and make sure it is showing as “Added”.

image
image628Ă—340 19 KB

Make sure the ruleset in which you published the component is present in the application.

Also try from incognito window and verify if the result is still same.

5

Go to Library > DX Components in Pega and check that your component shows as “Added” — if it doesn’t, it was never properly registered, which is why Pega throws the Component Not Found error. Next, confirm that the ruleset you published the component into is actually included in your application’s ruleset stack, since Pega can’t load a component from a ruleset the application isn’t using. Finally, open the app in an incognito browser window to rule out cached files causing the issue. Following these three checks in order should resolve the problem.