Client Extension fails to deploy when extension name is too long

Legacy Knowledge Base

Published Jun. 30, 2025

Client Extension fails to deploy when extension name is too long

Written By

Tony Ng

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

When naming a Client Extension, the extension will fail to deploy if the name is too long.
For example, when the extension is named "long-extension-name-landingpageredirect-global-js", running lcp deploy will fail saying the service is not found.

Environment

Liferay SaaS

Resolution

Client Extension Domains need to be less than 61 characters. This INCLUDES the extension domain, so any client extension created needs to have its extension name and domain be less than 61 characters in total.
For example, .example-organization-portal-extprd.lfr.cloud is 45 characters for the extension domain. this means any client extension created would need to be under 16 characters. This means the "long-extension-name-landingpageredirect-global-js" extension name would be too long.