Troubleshoot issues
The Troubleshooting page shows what failed, why, and how to fix it. It connects failures to the behavioral patterns NimbusWiz learned about the system during assessment, so if something predicted this would be a problem, you'll see that here.
Start with the Active Issues section. Pick an issue, follow the suggested remediation, then run a new scan to see if it's fixed.
Before you begin
All roles can view this page. To run a new scan, you need Operator or Admin access.
Open the Troubleshooting page
In the sidebar, select Troubleshooting.
When NimbusWiz routes you here from a failed assessment or deployment, the log viewer is pre-filtered to the relevant system.
Active Issues
The Active Issues section lists current issues detected across your fleet. Each issue card shows:
| Field | Description |
|---|---|
| Issue name | A short description of the failure type. |
| Severity | Critical (red) or Warning (yellow). |
| Affected systems | The systems currently experiencing this issue. |
| Occurrences | How many times the issue has been recorded. |
| Last seen | When the issue was most recently logged. |
To open the System Detail page for the primary affected system, select View [system-name] on the issue card.
Suggested Fixes
The Suggested Fixes section appears below Active Issues. When NimbusWiz identifies a likely cause for an active issue, it generates action buttons that link directly to the relevant remediation page.
For example, an issue with a system's stability score shows buttons like:
- Scan nimbus-dragon now: Navigates to the System Assessment page.
- Apply Extended Operation to nimbus-dragon: Navigates to the Modernization page.
- Schedule cleanup window: Navigates to the Automation page.
To go directly to the relevant page, select an action button on the suggested fix card.
Use the log viewer
The log viewer streams system events, errors, and NimbusWiz platform messages in real time. Entries appear in reverse chronological order, most recent at the top.
Each entry shows:
| Field | Description |
|---|---|
| Timestamp | The exact date and time of the event in UTC. |
| Level | Error, Warning, or Info. |
| Source | The system or NimbusWiz component that generated the entry. |
| Message | A plain-language description of the event. |
Filter the log
To narrow the log to relevant entries, use the filter controls above the viewer.
| Filter | Options |
|---|---|
| Keyword | Free-text search across all log message fields. |
| Level | All Levels, Error, Warning, Info. |
| System | All Systems, or a specific registered system. |
Common failure conditions
Match your condition below and apply the remedy.
| Symptom | Cause | Remedy |
|---|---|---|
| Deploy button is inactive | The simulation hasn't passed for the selected profile. The deploy gate can't be bypassed. | 1. Open the Modernize page for the system. 2. Select Run it for me on the profile card. 3. If the simulation fails, switch to a less aggressive profile, for example Stable instead of Performance, and run the simulation again. |
| Assessment shows High-risk components and blocks progress | One or more components in the dependency graph are marked High-risk and don't have an accepted remediation path. The assessment gate fails. | 1. Open the risk heatmap table on the System Assessment page. 2. Address each High-risk component listed. 3. Run a new scan. NimbusWiz preserves previous scan results in history. |
| System status stays on "Scanning" after the expected duration | The scan is still running in the background, but the progress indicator reset because you navigated away from the page before the scan completed. | 1. Wait for the status to update in the Systems List. 2. If the status hasn't updated, return to the System Detail page to see current progress. 3. If the status doesn't resolve within 15 minutes, re-run the scan. |
| Deployment fails mid-rollout | A dependency failed during the Executing Upgrade or Monitoring stage. NimbusWiz flags the failure in the log viewer and, if the failure matches a known pattern, in the Active Issues section. | 1. Open the log viewer and review the entry for the failure. 2. If a suggested fix appears in Suggested Fixes, select the action button to open the recommended remediation workflow. 3. Re-run the deployment, or roll back if rollback is still available. |
| Simulation result disagrees with Quirk Profile behavior | The simulation projection was generated before the most recent Quirk Profile update, or the Flight Profile has changed since the simulation ran. | 1. Return to the Modernize page. 2. Select Run it for me again to regenerate the projection with the latest data. |
| Action button is missing or disabled for a specific user | The user's current role doesn't grant the required permission, for example a Viewer trying to run a scan. | 1. Check the Current Role badge at the bottom of the sidebar. 2. To request a role change, contact an Admin. 3. See Getting started for the role requirements for each action. |
Diagnostic Tools
The following tools are planned features:
| Tool | What it does |
|---|---|
| System Health Check | Runs a full health check across the system's core subsystems. |
| Network Diagnostics | Tests network connectivity, latency, and packet loss. |
| Performance Profiler | Captures a performance profile to identify bottlenecks. |
| Dependency Checker | Verifies that all dependencies are present and at compatible versions. |
| Configuration Validator | Validates the system's configuration against expected values. |
| Log Analyzer | Scans recent logs for known error patterns. |
The Diagnostic Tools are planned features currently in progress.
Re-assess after resolving blockers
After you address issues through the log viewer and suggested fixes, return to the Systems List and run a new scan. NimbusWiz creates a fresh assessment record. Previous scan results are preserved in history and aren't overwritten.
When to contact support
If no fix resolves the issue after two attempts, contact your NimbusWiz administrator. For platform-level issues, server errors, data discrepancies, or persistent Critical alerts with no clear cause, see the support contact details in Getting help.