Platform: ClawCloud Japan Zone (ap-northeast-1)
Issue: Workspace Dashboard vs App Launchpad discrepancy & Service Inaccessible
Hi everyone / Support Team,
I’m facing a strange issue today on my containers in the Japan zone.
Current Situation:
App Launchpad View: I have only created/managed 2 containers. Both are showing as "Running" .
Workspace Dashboard: Under "Pod in current workspace", it shows 3 Healthy containers.
Access: I cannot access my service via the public container URL （I think pod is not deplyed right）.
What I did:
I performed restart and update operations on my containers today. The UI logs showed "Update successful" / "Restart successful".
Even though the Launchpad says "Running", the service is actually down.
Question:
It seems there is a "ghost" or orphaned Pod (the 3rd one) stuck in the workspace that is causing a routing conflict or blocking the actual 2 containers from working properly.
Since I cannot see this 3rd container in the App Launchpad UI, how do I delete or remove this extra "Healthy" pod? Is there an API command or a specific support ticket needed to clear the stuck pod?
Thank you for your help.