Checks, runs and node traces
Submit runs and inspect inputs, results, execution history and node states.
- Last updated
Check the current draft
Open a workflow in Material Expert and select Check in the toolbar. The platform checks nodes, connections, required parameters and variable sources, and identifies the draft revision checked.
The panel separates errors and warnings. Select an issue to locate its node, fix the settings and check again. Results from an earlier check do not validate subsequent edits.
A check examines configuration; it does not execute calculations.
Submit a test run
- Confirm the draft is saved.
- Open Test run → Run inputs.
- Complete the fields defined by User Input and wait for required uploads.
- Review the inputs and calculation size, then start the run.
- Follow waiting, execution and completion states in the progress view.
A test run executes the workflow. Use a small, inspectable input when validating structures and connections.
Inspect results and the node trace
Select a node in Trace to follow where its data came from and what changed. Structure results may include a 3D view, cell information and files. Use the relevant result cards for other output types.
Reopen previous runs
Open Run history and select an execution. A workflow may have several runs; compare their times, states and inputs before comparing outputs.
A previous run still represents its original configuration after you edit the draft. If the page identifies an earlier draft revision, run again to verify current changes. Keep run identifiers to distinguish outputs from different inputs and settings.
Verify individual nodes and handle failures
The single-step action in node settings helps inspect an individual node's input and output. When it requires upstream results, select an available source run or complete the preceding steps. Follow a successful single-step check with a full workflow run to verify connections and final outputs.
For a failed run, locate the failed node, read its error or logs, and resolve input, parameter or dependency issues before rerunning. After cancellation, check the final state before submitting another execution.
See Reading research results before using outputs in research comparisons, and retain methods, units and inputs alongside results.