Diagnose

Diagnose Directum RX instability by validating service health, deployments, and log errors.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dunaevdmitriys-dev/directum-mcp-server --skill diagnose-dunaevdmitriys-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Diagnose
Source: https://github.com/dunaevdmitriys-dev/directum-mcp-server/tree/main/skills/diagnose
Command: npx skills add https://github.com/dunaevdmitriys-dev/directum-mcp-server --skill diagnose-dunaevdmitriys-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly find why your Directum RX environment is failing or unstable by checking service health, deployed packages, and the most relevant log errors.

Core Features & Use Cases

  • Service health diagnosis: verifies the status of platform services using Launcher commands and identifies DOWN/PARTIAL states.
  • Deployment validation: checks which solutions are actually deployed and flags missing or outdated deployments.
  • Log-driven error triage: extracts recent ERROR/WARN/Exception signals from current logs and maps them to targeted recovery actions.

Typical use cases: after a failed update, after containers restart issues, when users report access/timeouts, or when deployment seems to have “nothing running”.

Quick Start

Run the Diagnose skill by providing your Directum Launcher path as launcher_path and, if available, a short symptom description in symptom, so it outputs a structured diagnosis with recommendations.

Frequently Asked Questions about Diagnose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose Directum RX service health after a failed deployment?

To diagnose Directum RX service health, you need to run Launcher commands via a specified launcher_path to verify the status of web, API, database, messaging, search, and storage components. The tool identifies DOWN or PARTIAL service states for recovery.

What is the best way to troubleshoot Directum RX access timeouts and instability?

Troubleshooting Directum RX access timeouts involves validating platform service health, checking deployed solution presence and freshness, and triaging error patterns from current.log to produce an action-oriented report with targeted recovery commands.

Can I check which Directum RX solutions are deployed and flag outdated packages?

Yes, you can check deployed solutions in Directum RX. The diagnostic process validates deployed package presence and flags missing or outdated deployments to ensure your environment is running the correct, fresh solution versions after updates.

Do I need a specific launcher path to triage Directum RX log errors?

Yes, you must provide a Directum Launcher path as the launcher_path parameter. This path is required to run Directum Launcher commands for service health checks and to extract recent ERROR, WARN, and Exception signals from current.log.

Why does my Directum RX stand show nothing running after containers restart?

If nothing is running after container restarts, the diagnostic tool can identify the cause by checking platform service health, validating deployed solution packages, and mapping recent log error patterns to specific recovery actions and commands.