The UEFN Session Inspector is a UEFN status and debugging tool that gives you visibility into the process of launching a session and live editing your project. Use it to confirm that your project's content is cooking, see when each module finishes, and diagnose issues if a Launch Session or Push Changes takes longer than expected.
Opening the Session Inspector
The Session Inspector is available from the Unreal Editor menu bar:
Tools → Live Edit Tools → Session Inspector
By default, the Session Inspector also opens automatically the first time you click Launch Session. You can toggle this behavior using the Settings cog in the upper-right of the panel:
Open when Launching Session — When enabled, the Session Inspector tab is automatically invoked each time a session is launched. Disable this if you prefer to open the panel manually.
The Session Inspector has two main sections:
Session Details
Session Cook Jobs
Session Details
The Session Details section provides at-a-glance information about your current live-edit session.
Open Project — The main project that is currently open.
Session Status — The current state of the Live Edit connection to the server and client. While work is in progress, a spinner is shown and the status describes the current step (for example, Waiting for session server, Waiting for all modules to be cooked and the server to load content, Waiting for client to be ready, Waiting for final content initialization). When everything is ready, the status reads All content service work finished. Server and client are now running. If something goes wrong, the status shows the error message and an error icon; full details are preserved in the tooltip and the Output Log.
Session Wall Time — The amount of time it took (or is taking) to complete the most recent Launch Session or Push Changes event. The timer runs from the moment you click Launch Session or Push Changes until all modules have been cooked and downloaded.
Session Cook Jobs
The Session Cook Jobs section provides information about the cook status of your project's module.
Each module is cooked once per platform, so the section is presented as a hierarchical tree view: the module is the parent row, and each platform-specific cooked artifact is a child row beneath it.
Module (displayed with its public Verse Path if available)
Platform Artifact 1
Platform Artifact 2
…
If your project depends on content from FAB, those dependencies appear as additional modules in the tree, each with their own platform artifacts. The columns provide information about each artifact, and the parent Module row displays a summary value across its children.
Columns
Version — The version of the artifact currently required by the project. As a given module is iterated on, this version increments or decrements as appropriate based on what the project requires.
Wall Time
For artifacts, this is the amount of time the artifact is taking to cook. If the artifact was retrieved from cache, this is the time it took to cook when it was cooked.
For parent Modules, the wall time is not a cumulative value across the underlying children. Instead, it's the wall time spent waiting for a cook during the most recent cook of one of its child artifacts. If all artifacts were retrieved from cache and not cooked, a Module's Wall Time is 0.
Completion Date — The time the artifact's cook completed. Note that if an artifact hasn't required a cook for a long time, this date could be far in the past — that's normal.
Status — The result of the cook. Possible values:
In progress — The cook is running.
Succeeded — The cook completed successfully.
Failed — The cook failed.
Unknown — The status of the cook cannot be retrieved. (Most common with FAB content.)
For parent Modules, the worst-case status across all child artifacts is displayed.
A cache icon is shown when an artifact was retrieved from cache and a cook wasn't needed. The parent Module only shows a cache icon if all underlying artifacts were retrieved from cache.
Troubleshooting tips
If Session Status shows an error, hover the row to see the full message in the tooltip, and check the Output Log for additional detail.
If a single artifact's Status is Failed, that module's row will also report Failed — start your investigation with the failing child artifact.
A long Session Wall Time combined with many In progress rows usually means the bottleneck is cook throughput; cached artifacts complete almost instantly and display the cache icon.