Start with the summary#
Check whether the run completed, whether any assets reported errors, and whether any packages failed to save. A cancelled run is incomplete even when its processed rows succeeded.
Read problem rows#
| Status | Next step |
|---|---|
| OK | Compiled or verified cleanly. Check saving completed, then retry your workflow. |
| Warning | Read the details: compiler warnings, an asset a dry run would recompile, or repaired references that must be saved. |
| Error | Double-click the asset and read its compiler message. |
| Load failed | The asset could not be loaded. Open it individually to see why. |
| Skipped | Already up to date, or a Level Blueprint. A force-save may help if packaging still uses stale saved content. |
| Skipped (unsafe) | Leave the safety option enabled and inspect the named assets. |
A cancelled run is incomplete even when its processed rows succeeded; review completed work, then rerun when ready. The Details column provides more detail than the row's status alone.
Use the result list#
Turn on Problems only to show only Warning, Error, Load failed, and Skipped (unsafe) rows. After a run with problems, the list switches to it automatically. Double-click a row to open its asset, or right-click it for more options. Use Copy to copy the visible rows for a report.
Understand dry-run limits#
A dry run checks the state of loaded assets. It does not compile them and does not perform every safety check used during a real run. An all-clear dry run does not guarantee that packaging will succeed.