Code 502

The `code 502` error indicates that the stream push from the rendering server timed out. This is typically caused by an application that takes too long to start on the local rendering server, or by the application failing to launch locally on the rendering server altogether.

## Cause 1: The Stream Push Timed Out

If the application on the local rendering server takes too long to start, the stream push may exceed the default timeout threshold and trigger a `code 502` error.

### Solution

Open the **Rendering Service Manager** and increase the streaming timeout value to `300000` (milliseconds). This allows more time for slow-starting applications to initialise before the connection is dropped.

## Cause 2: The Application Cannot Be Started Locally on the Rendering Server

If the application fails to launch locally on the rendering server, no stream can be established, resulting in a timeout error.

### Solution

Connect to the rendering server using a remote management tool (such as Sunlogin, TeamViewer, or VNC) and attempt to launch the application locally. Observe whether the application starts successfully and check for any error messages or missing dependencies.

## Notes

- If the application starts locally but the error persists, consider increasing the streaming timeout value further.
- If the application fails to start locally, resolve any application-level issues on the rendering server before retrying.