← Back to Pipeline Explorer

Troubleshooting

Quick links to the most common issues. Each page walks through likely causes in order of frequency and gives concrete resolution steps.

Tree and discovery

• Empty pipeline tree — The view shows (0) counts even though your project has handlers.
• Build errors after installing — The solution built cleanly before installation; now it doesn’t.

Server and runtime

• Server startup failed — The bundled background server can’t start or crashes immediately.
• Profiler not attaching — Runtime profiling shows no events even though your application is running.

Licensing

• License activation failed — Your license file was rejected, the seat limit was reached, or activation couldn’t complete.

---

Diagnostic checklist before reporting

If you plan to open an issue at the GitHub repository, collecting these four items up front cuts the round-trip in half:

1. IDE and extension version
   • VS Code: Help → About and Extensions view → click the extension → version on the right.
   • Visual Studio: Help → About Microsoft Visual Studio, then Extensions → Manage Extensions → Installed → DSoftStudio Mediator Pipeline Explorer for the extension version.
2. Mediator output panel (last 50 lines)
   • VS Code: Ctrl+Shift+U → select Mediator in the dropdown.
   • Visual Studio: View → Output → select Mediator in the dropdown.

3. Package list

   dotnet list package | findstr Mediator
   

   (Use grep Mediator on macOS / Linux.)

4. OS and architecture

   uname -a              # macOS / Linux
   systeminfo | findstr "OS"   # Windows
   

---

← Back to Pipeline Explorer