Resolve Missing Artifacts, Links, and Results

R2026b

Issue

The Model Design and Model Testing Dashboards use a digital thread to analyze artifacts—including models, code, requirements, tests, and results—that are part of the model design and testing workflow for software units and components.

An artifact or a link between artifacts might not appear in the dashboard or contribute to the metric results if:

The artifact or link is not supported by the digital thread.
The artifact or link is not part of the workflow.

Possible Solutions

If you expect a link or an artifact to appear in the dashboard and it does not, try one of these solutions.

Save Artifacts in Project

The digital thread analyzes only artifacts that are saved inside the project or referenced projects.

Save changes to your artifact files.
Make sure that your artifacts are in the project or referenced projects.
Check that any referenced projects have unique project names.

Note

By default, the digital thread analyzes files inside your project folder, even if the files are not on the path or are not added to the project. If your project uses the TOML metadata format, you can exclude files and folders by updating the matlab.toml file. For more information, see Exclude Files and Folders. If you want to exclude certain models from the dashboard, specify which models are units or components by labeling them in your project and configuring the dashboard to recognize the label, as shown in Specify Models as Components and Units.

Address Artifact Issues

The digital thread needs to be able to find, analyze, and trace artifacts.

To investigate artifact issues, click the Traceability tab and click Artifact Issues on the toolstrip. For more information, see View Artifact Issues in Project.
Address warnings and errors.
- Warnings indicate that the digital thread does not support that specific artifact, modeling construct, or relationship.
- Errors indicate that the digital thread could not properly analyze artifacts, trace artifacts, or collect metrics, so the metric data in the dashboard widgets might be incomplete.

Check If Artifact Can Contribute to Metric Results

Only artifacts directly related to the unit or component contribute to the metric results in the dashboard. For information on what qualifies as a unit or component, see Categorize Models in Hierarchy as Components or Units.

Artifacts in the following folders in the Artifacts panel are for reference only. These artifacts are not directly related to the unit or component that you selected and do not contribute to the metric results in the dashboard:

Functional Requirements > Upstream
Tests > Others
Test Results > Others
Trace Issues

If you expect an artifact to appear in a specific folder and it does not, see Manage Project Artifacts for Analysis in Dashboard.

Avoid Unsupported Features

The digital thread does not support certain features because they prevent it from properly identifying and tracing the relationships between artifacts.

Unsupported features have:

Unsaved information — The digital thread needs to capture the attributes and structure of the artifacts in your project. If an artifact has unsaved changes or relies on unsaved information, the digital thread cannot reliably use the information for artifact traceability analysis.
Ambiguous relationships — The digital thread needs to capture the traceability relationships between the artifacts in your project.
A limitation in the digital thread — The digital thread is unable to analyze certain artifacts and relationships. For information on the digital thread, see Monitor Artifact Traceability and Detect Outdated Results with Digital Thread.

Affected Artifact	Unsupported Features	Rationale
Model	SLX model files created before R2016a	Limitation
	MDL model files for Simulink^® created before R2021b	Unsaved information — The digital thread requires model files that conform to the Open Packaging Conventions (OPC) interoperability standard. MDL files conform to OPC starting in R2021b.
	MDL model files for System Composer™	Limitation
	Model callbacks	Unsaved information and ambiguous relationships
Library	Library forwarding table	Unsaved information and ambiguous relationships
Test	MATLAB^®-based Simulink test	Limitation
Test	Scripted test iterations	Limitation — The digital thread cannot identify individual results from scripted iterations, so the dashboards show the test as one result. If iterations are table-based, the digital thread can identify each iteration and its results, so the dashboards can show those iteration results individually.
Test Harness	Test harness on a library block instance subsystem	Ambiguous relationships
Test Result	Test results from an unsupported test	Limitation
Coverage Result	Aggregated coverage for external C code, such as S-function and C Caller blocks	Limitation — You must manually verify any external C code that you develop.
Coverage Result	Coverage results for shared code files	Limitation
External MATLAB Code	Methods declared in separate files	Limitation
Requirement links	Embedded links (requirement links that are saved directly in the model file)	Limitation
	Links to requirements that are saved externally and linked using the Requirements Management Interface (RMI)	Limitation
	Links to custom requirements that you defined using stereotypes	Limitation
	Links inside: Requirements Table blocks Test Sequence blocks Test Assessment blocks	Limitation
	Links in requirement files that have the `.req` extension	Limitation — REQ files are from the legacy Requirements Management Interface (RMI). Save the links in an SLMX file or create them in an SLREQX file that has the requirements.
	Links to models for which the model file extension changed	Limitation — If a requirement is linked to a model with the file extension `.slx`, but you change the model file extension to `.mdl`, the digital thread lists the requirement link as unresolved. Modify the requirement link to reference the expected model file and resave the requirement link.
	Links to unsupported modeling elements	Limitation
	Custom link types that you defined by using stereotypes	Limitation
	Requirement link to a justification	Limitation — If a requirement is linked with a justification and not linked to a test, the requirement appears as unlinked in the metric results.
	Ambiguous links: Link set shadows another loaded link set of the same name Requirement set shadows another loaded requirement set of the same name Link is not on the project path or is only temporarily on the project path Link path format is an absolute path Source artifact of the link set does not use the default link file name and location	Ambiguous relationships
Links	Symbolic file links in a project, such as shortcuts	Limitation
Sequence Diagrams	Links from sequence diagram elements (lifelines, gates, messages, and fragments) to requirements, and links from lifelines to System Composer components	Limitation — The digital thread does not decompose sequence diagrams, so traceability links involving sequence diagram elements are not analyzed.