Start or stop a Cloud project and understand its connection status
Read the project computer indicator, control automatic start, and handle connection or permission errors without interrupting work unnecessarily.
Read the project computer indicator
The computer icon in the Cloud project list and the DDS or ALcad footer describes the project runtime. Gray means offline or stopped, yellow means starting, green means running, and orange means stopping. A red exclamation indicates that a status or control request failed; hover for the reason and open connection diagnostics.
A running project computer does not mean that a job has run or succeeded. Check each job's status and output separately. Cloud RTL simulation is not open to customers yet. A missing project is also different from a stopped runtime: first confirm the selected account, organization and project access.
Choose whether opening a window starts the project
Opening a DDS or ALcad window starts a stopped project by default. In Settings, under Cloud runtime controls, turn off Start the project when opening a window if you want to inspect a window without automatic startup. This preference applies to the account and organization in the current browser; another browser may use a different setting.
Reading status or opening settings does not start the workspace. The preference does not grant permission or change server idle limits. Review the operation and usage information before explicitly starting managed work.
Stop only after checking active work
Click the computer for the intended project and inspect its queued or running jobs and terminal processes.
Use the offered Stop control. Cancel dismisses the stop decision and preserves jobs; Cancel jobs and stop explicitly requests cancellation and waits for cleanup.
Read the final state. A cancellation request or stopping indicator is not yet confirmation that the work has stopped.
Controls on a project row apply to that project, even if another project window is open. A manual Stop stays stopped while that window remains open. Closing a browser is not a substitute for reviewing or canceling a running job.
Recover from a connection error
Use Check again to read the current state before choosing an explicit retry. A start request may still be running even if its response was lost. Repeated Start clicks can obscure what happened.
For AUTH_DENIED, PROJECT_OWNER_REQUIRED or WORKSPACE_FORBIDDEN, check the organization and ask the owner to confirm access. For authorization-expired or authorization-changed errors, verify the account and refresh state before retrying. Keep unsaved edits and saved files intact.
Send private support the time and time zone, project identifier, visible error and operation identifier if shown. Connection diagnostics contain browser-observed control errors, not full VM or solver logs; include the relevant job record for a failed computation.