Diagnostic Codes
When an operation fails, DEP shows a classified diagnostic instead of a raw error. Each diagnostic has a code (for example DEP-RUN-OWNER), a title, an explanation, an outcome and a recovery path. This page lists all of them.
How to read a diagnostic
Diagnostics appear in the Problems (n) panel (bottom right), in the status line of the workspace, and in error banners such as:
Error: The operation could not be completed. DEP could not classify this failure safely. The outcome could not be
established; inspect current state before repeating the operation. [DEP-UNEXPECTED; diagnostic 80e48f1a-…]The bracket gives the code and a diagnostic ID. The ID identifies this single occurrence. It is stored in DEP's diagnostic journal and is included in a support summary.
The outcome tells you what happened to your data. This matters most before you retry:
| Outcome | Meaning | Safe to retry? |
|---|---|---|
not-applied | Nothing was changed. | Yes, after fixing the cause. |
rolled-back | A change started and was undone completely. | Yes. |
partially-applied | Some parts were changed. The diagnostic says which. | Inspect first. |
applied | The change happened, but a follow-up step failed. | Do not repeat the change. Fix the follow-up. |
unknown | DEP could not determine the result, for example after a timeout. | Inspect the current state before repeating. |
not-applicable | The diagnostic is informational. | — |
Severity is warning (the action was refused to protect you), blocked (a precondition is missing) or error (the action failed). Many diagnostics offer Go to recovery workspace and Copy support bundle.
Execution and projects
| Code | Title | Meaning and recovery |
|---|---|---|
DEP-RUN-OWNER | Stop the active session before changing execution | You tried to change the System graph or execution profile while a runtime or SoftwareUnit was active. Nothing changed. Stop the session in its owning System or Operator workspace, then select the profile again. |
DEP-PROJECT-RUNNING | Stop the active run before changing projects | The project still has a running, paused or faulted session. In System → System Engineering, cancel the run if needed, then stop the session. The current project stays open. |
DEP-PROJECT-SOFTWARE | Stop running software before changing projects | A customer software process is running. Stop it in Library → Software integration (process health) before opening another project. |
DEP-PROJECT-TARGET | Stop and reconcile the target before changing projects | A remote HIL runtime is active or its state is unresolved. Stop and reconcile it in Runs → HIL runtime. |
DEP-PROJECT-SAVE | Project could not be saved | DEP could not commit the change. The previous saved revision is still valid. Check disk space and write access, review the project state and save again. |
DEP-PROJECT-BUSY | Project observation is temporarily busy | The runtime is writing project data. The last displayed values are kept. Retry shortly. If it persists, stop the active session. |
DEP-EVIDENCE-LIMIT | Recording limit reached | DEP stopped recording before exceeding the project evidence budget. No samples were silently dropped, and committed evidence is kept. Stop the session, export its results, then use a fresh project copy or raise the limits in System → Run options → Evidence storage limits. |
DEP-REC-OWNER | System owner recovery required | The process that owned execution was lost or is unknown, for example after a crash. Resume is blocked. Use Reset, or Stop → Check → a new Run. |
DEP-REC-ACTIVE | Another System owner is active | The session belongs to another live DEP process, such as a second DEP window on the same project. Close that one before recovery. |
DEP-CFG-OWNER-ACTIVE | An execution owner is still active | Stop the execution owner before changing this configuration. Open Runs → Execution & HIL to see it. |
DEP-CFG-PROJECT-CHANGED | The active project changed | The project changed while a dialog was open. Refresh the System and review the operation again. |
DEP-CFG-REVISION-CHANGED | The System changed after review | Someone or something changed the System after you reviewed a change, for example a road in Vehicle Studio. Refresh and review again. The old review cannot be applied. |
DEP-CFG-PROFILE-MISMATCH | This example requires MIL | Select the MIL profile in System Engineering before creating this example. |
DEP-DESKTOP-BRIDGE | Desktop service is unavailable | The operation needs DEP's desktop service, which is not responding. Save if possible, restart DEP and retry. |
DEP-UNEXPECTED | The operation could not be completed | DEP could not classify the failure safely, so the outcome is unknown. Inspect the current state before you repeat the operation. Check Runs → Execution & HIL → Diagnostics, and send a support summary if it happens again. |
Scenarios and tests
| Code | Title | Meaning and recovery |
|---|---|---|
DEP-TEST-PROFILE | Scenario execution needs attention | Scenarios run only in a local MIL or SIL profile. Select MIL or SIL in System Engineering, then in Scenarios use Check selected scenarios. HIL scenarios cannot run here. |
DEP-TEST-DEFINITION | Scenario step needs correction | A scenario step is incomplete or invalid, for example a Check output step without an expected value. The message names the scenario, step and reason, such as step 3 (assert): Expected value must be a finite number. Nothing was saved. Correct the step in Scenarios → Scenarios & validation and save again. Some versions report the same problem as DEP-UNEXPECTED. |
DEP-CHARGE-MIL | Charging tests need attention | Stop the current MIL run in System before creating charging tests. |
Models, libraries and integration
| Code | Title | Meaning and recovery |
|---|---|---|
DEP-SIL-IMPLEMENTATION-MISSING | SIL implementation is not ready | A component has no compatible executable SIL implementation. Assign one in Integrations… → Software implementations, or switch back to MIL. |
DEP-SIL-SETUP | SIL setup needs attention | The SIL assignment or implementation selection could not complete. Review it in Integrations… → SIL assignment. |
DEP-SIL-REMOTE | Remote SIL participant requires recovery | A remote participant could not confirm execution, so its outcome may be unknown. Check the connection and participant service, then use Reset all participants in Coordinated SIL before running again. Committed samples are kept. |
DEP-SIL-REMOTE-CONFIG | Remote SIL credentials need attention | The TLS files for a remote participant are missing or invalid. Check the saved CA, client certificate and private-key environment-variable references. |
DEP-FMI-WIN64-MISSING | Windows FMU binary is missing | The FMU has no Windows x64 binary. Ask the supplier for a win64 FMU, or build one, for example by exporting from Model Designer. |
DEP-MAP-CONFLICT | Signal mapping needs attention | One or more canonical mappings conflict or point to an endpoint that no longer exists. Fix them in System → Signal mappings (filter Status = Conflict or Broken). |
DEP-MODEL-SOURCE | Model source needs attention | The selected implementation has no editable source in Model Designer. Retain its source in Library Center → Source and copies, or edit it in its own editor. |
DEP-OBJ-REPLACEMENT | Replacement needs review | An implementation replacement could not complete. Refresh the review and resolve the reported dependency. |
DEP-OBJ-LIBRARY | Object Library needs attention | A Library Center action failed. Select Refresh library and review the source or definition before retrying. |
DEP-SSP-REVIEW | SSP package review needs attention | Select and review the SSP package again. Check its format and compatibility findings before importing. |
DEP-REQ-IMPORT | Requirements import needs correction | Choose the worksheet, map the ID and description columns and correct the reported fields. Your current baseline was not replaced. |
DEP-MODEL-VERIFY | Numerical verification did not complete | Review the test inputs, expected values and saved model. No numerical report was recorded. |
DEP-MODEL-BEHAVIOR | Model behavior is incomplete | The proposed model did not pass behaviour acceptance. No model was created or exported. |
DEP-AI-PROPOSAL | AI model proposal needs correction | The generated model failed structural validation. Nothing was created. Regenerate and review the requirement links. |
DEP-AI-PROVIDER | AI connection needs attention | Review the saved AI connection, model ID and data-sharing approval in Settings → AI connections. |
Charging, targets and other integrations
| Code | Title | Meaning and recovery |
|---|---|---|
DEP-CHARGE-API | ChargeLink API needs attention | Check that the ChargeLink service is running and that the saved connection (executable and Integration API address) is correct. Use Check API in the EVSE console. |
DEP-TGT-SESSION | Target operation needs attention | Inspect the target session in Runs → HIL runtime before retrying. |
DEP-TGT-TIMEOUT | The target did not respond | Check the target address, network and API service. A timeout does not prove that the target has stopped. |
DEP-LICENSE | Licence action needs attention | The licence operation did not complete. Review the licence file or server settings in Settings → License & ownership. |
DEP-VIEWER-WORKFLOW | Vehicle Studio needs attention | Review the Vehicle Studio connection and the active execution owner. |
DEP-ROAD-WORKFLOW | Road demo needs attention | Inspect the road demo state and continue from the reported stage. DEP does not invent vehicle motion. |
Licence result codes
The licence page can show these results for an installed licence:
| Code | Meaning |
|---|---|
LIC_OK | Valid licence. |
LIC_GRACE | The subscription has expired but is within the 14-day grace period. Renew it. |
LIC_EXPIRED | The licence has expired. |
LIC_WRONG_MACHINE | The licence is bound to another computer's Machine ID. |
LIC_KEY_NOT_GENUINE | A USB stick is not a provisioned DEVlink licence key. |