Troubleshooting
Why is the log viewer empty?
Check your active filters. The most common causes:
- The Level filter excludes the entries you're looking for. Set it to All Levels to see every severity.
- The System filter is set to a different system. Set it to All Systems, or change it to the system you're investigating.
- The Keyword field has a search term that doesn't match any entries. Clear it.
The Troubleshooting log viewer doesn't have a time-range filter. Entries appear in reverse chronological order, most recent at the top.
I can't see the Register a system button.
The Register a system button is only visible to Operators and Admins. Viewers don't have access to this action. Check your Current Role badge in the sidebar. If you're a Viewer, contact your Admin to request an Operator or Admin role.
NimbusWiz is showing data I don't recognize.
Check whether Demo Mode is active. When active, the sidebar button turns blue and shows "● Demo Mode Active." A blue banner also appears at the top of the page. To return to your real data, select the button to toggle Demo Mode off.
I forgot to copy my API key. What do I do?
The full key can't be retrieved after generation. NimbusWiz doesn't store it.
To recover, revoke the existing key in Developer Hub > API Keys and generate a new one. Update any pipelines or integrations using the old key before revoking it to avoid downtime.
API key generation and revocation are planned features currently in progress. The UI controls are present, but they don't save or revoke keys yet.
A scan keeps failing on the same system. What should I try?
- Check the assessment results for the specific failure reason.
- Open the Troubleshooting page and filter the log to the affected system.
- Review the Quirk Profile context surfaced in the Modernization Advisor for patterns that match the failure.
- Check network connectivity between NimbusWiz and the system.
- If the failure persists after two scan attempts, contact your Admin. The issue may need platform-level investigation.
The Apply buttons are inactive after the simulation.
The Apply [Profile] Profile buttons only become active after the simulation passes for that profile.
If they remain inactive after a simulation run:
- Check whether one or more safety checks failed (dependency compatibility, disk space, backup, or quirk conflicts). If so, the simulation didn't pass.
- Switch to a less aggressive upgrade profile, for example Stable instead of Performance, and run the simulation again.
- Refresh the page. In rare cases a stale UI state can make a button look inactive after a successful simulation.
I removed a user but their pipelines are still running.
When a user is removed, their pipelines remain active and are reassigned to the Admin who removed them. To stop a pipeline, go to Automation, find the pipeline, and either deactivate or delete it.
For full guidance, see Manage automation in the Admin guide.
User removal is a planned feature currently in progress.