Digital Design Studio Diagnostics

Use the selected host’s available analysis operation to create a new run; preserve its input identity, engine version, diagnostics and saved output. Cloud jobs require an offered operation, permission and QUOTA. Cloud UVM and the Physical coordinator runtime remain unavailable. Opening a saved run, a setup dialog or a tool catalogue does not submit a job, and a rejected or unsupported action is never a successful zero-valued result.

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.

Workspace · Settings

Find the cause

1. Open Console and enter the notification code, tool name, or part of the message in the search field.

2. Select a severity to narrow the results. Clear the search and select All levels to show the full session history.

3. 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

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.

Use diagnostic records and Cloud MCP only through the supported authenticated route for the selected project. Read, append and delete retain their own permissions; confirm the observed record boundary before deletion.

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.

Prepare a useful support report

Include the product version, operating system or browser, Local / My PC, Cloud, or legacy WSL host, operation, timestamp with timezone, diagnostic code, and a minimal sequence that reproduces the problem. For remote work, include a job or operation ID if available. Separate “request accepted,” “job completed,” and “result saved” when explaining the last successful step.

Copy only the relevant redacted log excerpt. A screenshot of a graph is useful for layout issues; the original result and input identity are more useful for a numerical discrepancy. Do not include account tokens or an entire private project.

Simulator and company AI messages

For a Windows Testbench run, expand Simulator log for compilation, include-path and simulator errors. Company AI shows localized notices for an unavailable task, consent, country or age, exhausted QUOTA and temporary failures. Retain the visible message and time, without private prompts or source. See the testbench guide and company AI guide.

Using Digital Design Studio 2.0.2

A fatal error or failed save shows an explicit recovery state; keep unsaved work and inspect the last confirmed save. To report a problem, review the report and choose Send explicitly. The report goes privately to support and is deleted after 30 days. Automatic report data contains only predefined error codes, components and stages, where it happened (desktop app or Cloud) and what happened (an unexpected stop or a failure to save), product/platform/version information, occurrence counts and times, project-protection state and a randomly generated report ID. Exception messages, source excerpts, file paths, stacks and recent-action text are not collected. An optional comment is written by you and sent exactly as you explicitly confirm it; do not include design code, NDA material, credentials or personal data. Code-like lines are highlighted for a choice to remove those lines, send unchanged or cancel; this does not guarantee detection or removal of code. Comments are disabled for protected or unconfirmed projects, which can send only predefined automatic data. We store the comment confirmation time and version with the report. A Community post is public and is a separate action. Closing a dialog or viewing an error does not submit a report.

2.0.2 environment support

Review and send a private error report

Digital Design Studio 2.0.3 displays the complete report before sending, highlights lines in user comments that may contain code or credentials, and keeps long comments visible while blocking submission until shortened.

1. After an unexpected stop, choose Report this problem privately to open the review dialog. If a save fails because the file could not be written, the review dialog opens by itself.

2. Read the predefined fields under What will be sent. The Complete report section below your comment is already open and shows the full report. It is hidden while your comment is longer than 4,000 characters.

3. If adding a comment, enter a brief description. If the text exceeds 2,000 characters, it remains in the field but submission is blocked with Your comment exceeds 2,000 characters. Shorten it before sending.

4. If the comment contains lines that look like code, keys or tokens, the preview highlights them with Highlighted lines may contain code or credentials. Choose how to send your comment. Choose Remove highlighted lines and review to remove those lines and check the comment again before sending, or choose Send unchanged to send the comment as written.

5. If you wrote a comment and no line is highlighted, select I have reviewed the complete report and my comment., then choose Send report. Without a comment, choose Send report. While lines are highlighted, use one of the two choices in step 4 instead.

Error reports are transmitted privately to Altifigence and deleted 30 days after receipt. Automatic data contains only predefined error codes, stages and version information. Error messages, source excerpts and file paths are not collected. Comments are disabled for NDA-protected projects and when a project's protection cannot be confirmed. Line highlighting is an assistive review filter and does not guarantee complete detection of sensitive data.

See Diagnostics for diagnostic codes and retention rules.