Issue

From the Mendix Portal > Environments page, the operator license may display as expired status when using Mendix Operator version 2.22 or earlier, as shown in the image below. This status could self-correct within a short period (e.g., less than one hour) without any intervention.

Environment

Applications hosted in Mendix on Kubernetes

Cause

The status shown in the portal is a direct reflection of the licenseStatus > mode field within the Mendix App Custom Resource (CR) in the Kubernetes cluster. The operator itself controls this field.

"licenseStatus": {
"licenseID": "7cff80bc-8146-44be-9e5c-fb70155e31d9",
"mode": "Licensed"

In theory, the Mendix operator license is perpetual and does not expire. Once applied, an operator license remains active indefinitely. The exact mechanism that causes the operator to temporarily set the status to "Expired" is not fully determined. It is suspected to occur during the operator's internal reconciliation cycles.

The operator license status has no impact on the runtime state or availability of deployed Mendix applications. Applications continue to run normally during this period.

Solution / Workaround

The available options for resolving or addressing the transient license status depend on the current Operator version and upgrade readiness.

Upgrade to Operator version 2.23 or above (recommended)
- Starting from Operator version 2.23, Operator licenses are no longer needed. Upgrading will eliminate this scenario.
The Operator version stays in 2.22 or below
- Refresh the portal to manually trigger a fresh fetch of the status from the cluster. This may immediately restore the correct "Licensed" status.
- If the issue persists, supply log files for further investigation.

Internal information related

268797
C0161BEMQ4B/p1767860253469489

Additional information

Mendix documentation: Operator License
Related KBA: Mendix for Private Cloud (Mx4PC) licensing questions on expiration, trial period and renewal

Expired Operator status on Mendix Portal