Cloud Application Exit Detected

When the web client displays a "Cloud application exit detected" notification, it means the rendering application on the server has terminated unexpectedly or has been closed. This can occur due to several configuration or hardware-related issues.

## Cause 1: The Application Is a Multi-Process Application

Some applications spawn multiple processes at runtime. If the rendering service is monitoring only the primary process and that process exits or hands off control to a child process, the service may incorrectly interpret this as an application exit.

### Solution

Enable **Exclusive Mode** in the Rendering Service Manager for the application. This mode ensures that the rendering session is bound to the application's full process lifecycle rather than a single process entry point.

## Cause 2: Incorrect UE Program Execution File Path

The Unreal Engine (UE) application executable path configured in the rendering service is incorrect. If the service cannot locate the correct executable, it may launch the wrong process or fail to monitor the application properly.

### Solution

Set the UE program execution file path correctly in the Rendering Service Manager. Refer to the following guide for detailed configuration steps:

[How to Set the Application Path](https://www.pingxingyun.com/contribute/detail?topicId=10107&categoryId=3)

## Cause 3: Rendering Node Uses a GT-Series Graphics Card

GT-series graphics cards (typically entry-level NVIDIA cards) are not supported by LarkXR's rendering service. Using an unsupported graphics card will cause the rendering application to fail or exit immediately.

### Solution

Replace the graphics card on the rendering node with a supported model. Refer to the following page for the list of supported hardware:

[Supported Graphics Cards](https://www.pingxingyun.com/online/sr3_2.html?id=384)

## Cause 4: Application Crash or Unexpected Exit

The application itself may be crashing or exiting on the server side due to internal errors, missing dependencies, or runtime exceptions.

### Solution

Connect to the render server directly and attempt to launch the application locally to verify whether it runs stably. Review any crash logs or error dialogs to identify the root cause of the unexpected exit.

## Notes

- If the application is multi-process, always enable Exclusive Mode to ensure proper session monitoring.
- Verify hardware compatibility before deploying a new rendering node to avoid graphics card-related failures.