Recover or delete saved RTL analysis results
Saved RTL analysis on Cloud is not open to customers yet. Read the guidance for existing stored records.
Saved RTL analysis on Cloud is not open to customers yet. The recovery steps below apply to existing records and only to actions actually offered by the selected project. Use the deletion section for completed stored Cloud results.
Start with the saved file
Save the .sv or .v source file and identify its top module.
Do not assume an unavailable control can be enabled merely by refreshing or changing the URL.
RTL simulation today
For RTL simulation, use the Windows testbench in First RTL simulation.
Read an existing record
If your project already has an analysis record, read its saved result and diagnostics. Reopening a stored result does not start a new run.
Generic cell count and logic depth are structural results; they are not measured silicon area, characterized timing or manufacturing approval.
Recover instead of creating a duplicate job
If the submission response was lost, use Recover submission or the existing job's refresh action.
If calculation finished but storage failed, use Retry saving result or Recover completed result, then confirm the saved path.
Use Saved analysis results to reopen a stored result without starting a new run.
For a queued or running job, Cancel analysis requests cancellation. Keep checking state until it settles.
Keep the saved source revision, estimate or job identifier and diagnostics. For support, send these identifiers and the visible error privately; do not send a full proprietary design unless an appropriate sharing route has been agreed.
Delete results you no longer need
Select the intended organization, project and completed Cloud job. Only the project owner can delete its stored results. Download any results you need before confirming the available deletion action. This action does not enable a new analysis that your environment does not support.
Queued, running or unsettled jobs cannot be deleted this way. If a retained artifact or workspace references a result, resolve that reference first. Deletion removes the stored job request, outputs, artifacts and related checkpoints, but does not delete the project's original source files.
After confirmed deletion, the old result is no longer readable; retrying that job does not restore it. If the response is lost, check the existing job and deletion state before retrying. Storage usage may take time to reconcile.
Deleting a whole project also cleans up its retained versions and Cloud results. Never-started queued work is held and cleaned up. Running or unsettled work is retained until it can be revisited; deleting a project is not immediate cancellation of every active job.
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.
For RTL simulation, use the Windows testbench in First RTL simulation. Cloud jobs require an offered operation, permission and QUOTA. Cloud UVM and the Physical coordinator runtime remain unavailable, and Cloud RTL simulation is not open to customers yet; for RTL simulation, use the Windows testbench. 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.