Hi Anup Adkar

This is a Mendix Operator to Runtime Pod communication issue on Kubernetes/Private Cloud.The app is running fine, but the Mendix Operator can't poll the Runtime pod's status API (getting HTTP 500), so the portal stays stuck spinning. From you message i conclude that

1.Pod is up and reachable

2.App is serving end users fine

3.The m2ee admin/status endpoint inside the pod is unhealthy.

Now primarly You need to check the Startup microflow->Disable After Startup microflow, redeploy & test.

Other checks worth to do are

1.Runtime version mismatch

2.Pod under memory pressure

3.Wrong adminPort in MendixApp CR

If not kindly share the runtime logs. I hope this helps

Hi,

This behavior typically indicates a runtime status reporting issue in the Mendix Operator, not an actual application problem.

Since your application is running fine, the issue is not with deployment itself but with how the Operator retrieves pod runtime status.

Root cause

The key error is:

runtime status cannot be retrieved: invalid response code: 500 Internal Server Error

This means the Mendix Operator is trying to query the runtime (via the runtime status endpoint), but the pod is returning HTTP 500, so the Operator cannot update the status correctly. As a result, the environment keeps showing “The resource is still processing”.

Common reasons

1. Runtime status endpoint temporarily failing
   
2. The app is up, but the internal status endpoint used by the Operator is not responding correctly.
3. Networking / service mesh / ingress issues
   
4. If you are using Istio, Nginx, or any proxy:

• Internal calls from Operator → Runtime may fail
• Leads to 500 responses

1. Mendix Operator / Runtime version mismatch
   
2. Incompatibility between Operator and Mendix Runtime can cause status parsing failures.
3. Heavy startup or blocked threads
   
4. If runtime is under load or stuck during health checks, status endpoint may fail intermittently.

checks / fixes

1. Verify runtime health endpoint manually

From within the cluster:

kubectl exec -it <pod> -- curl http://localhost:8080/

(or relevant status/health endpoint)

Check if it returns 200 consistently.

2. Check runtime logs

Look for:

• Exceptions during startup
• Thread blocking / long-running tasks
• Errors around request handling

3. Check Operator ↔ Runtime connectivity

• Ensure no network policies are blocking internal calls
• If using service mesh (Istio), check sidecar configs

4. Restart Operator pod

Sometimes the Operator gets into a bad reconciliation state:

kubectl rollout restart deployment mendix-operator

5. Validate version compatibility

Ensure:

• Mendix Runtime version
• Mendix Operator version

are officially compatible.

6. Temporary workaround

If everything else is fine:

• Restart the runtime pod
• Or redeploy

This usually clears the “processing” state.

This is a status synchronization issue between Mendix Operator and Runtime, not a functional problem with your app. The runtime is healthy, but the Operator cannot retrieve its status due to intermittent 500 responses. Fixing connectivity, health endpoint stability, or restarting the Operator typically resolves it.