Digital Design Studio Diagnostics#
Find operation details in Console and search notification codes and severity.
Overview#
When an operation fails, open Console in the bottom panel to inspect its details. Notifications give a short explanation and a code that you can search. Older installed versions may use different wording or lack these filters.
Find the cause#
Open Console and enter the notification code, tool name, or part of the message in the search field.
Select a severity to narrow the results. Clear the search and select All levels to show the full session history.
Read the technical details, correct the input or environment, and retry the operation when appropriate.
Engine and CLI messages are recorded in Console. Background checks do not open warning popups. A failed action that you started can open Console and add an entry to the footer notification center. Your notification settings control whether a popup also appears in the bottom-right corner.
Codes#
Code |
Tag |
What to check |
|---|---|---|
DDS-E100 |
engine |
The design input, execution setup and engine details in Console. |
DDS-W100 |
workspace |
File access, project state and the current file revision. Preserve unsaved changes. |
DDS-N100 |
network |
Connection and sign-in state before retrying. |
DDS-R100 |
runtime |
Whether the selected environment supports the operation and which setup is required. |
DDS-A100 |
application |
The operation details in Console before retrying. |
The code describes the affected area. The severity describes the outcome: info records status, success records completion, warning indicates an issue to check, and error indicates a failed operation.
An unavailable operation remains unavailable after its technical status moves to Console. Passing a preflight checks the request; it does not mean that a solver has run or that measured results exist.
Keep useful evidence#
In Cloud, Console searches saved project diagnostics as well as the latest 200 live observations in the current window. Saved records are retained for 30 days, up to 2,000 per project. Load older pages to continue a search; each Cloud page contains at most 100 records. Refresh after a connection failure. Saved records return when you reopen the project, while unsaved observations remain local to the current window.
Cloud sends up to 20 observations per batch. Each message is limited to 2,000 characters. Read-only project members can search saved records; editors can add records. Only project owners can delete records, and deletion covers the previously observed history boundary so newer records are preserved. Search filters do not delete entries. The MCP tools use the same project store with explicit tool permissions and smaller read pages of at most 40 records.
Saved records have immutable UUIDs. Repeating the same upload is safe; reusing an ID with different content reports a conflict. Repeated live status messages may update one entry in the current window without rewriting saved records. Common credential patterns and terminal controls are removed before storage, but do not include credentials, source files or AI prompts in diagnostic messages.
Desktop and local development hosts keep only the latest 200 live observations in the current window. Closing the workspace clears that history. Copy useful details before closing; it is not a permanent incident archive. Older versions may lack saved Cloud history. Availability follows the deployed Cloud service and your installed product version.