Troubleshoot Lab Management Upgrade Issues
Troubleshoot Lab Management Upgrade Issues
Use this article when Lab Management resources behave unexpectedly after an AIQ upgrade. Start by confirming whether the issue is data migration, permissions, node/device availability, or a stale browser/session state.
Common checks
- Confirm the upgrade completed successfully and review migration logs for warnings.
- Verify that labs, devices, nodes, and resource groups still appear with the expected names and assignments.
- Check user roles and permissions for teams that can no longer access lab resources.
- Confirm nodes and devices are online and registered after the upgrade.
- Clear stale browser sessions only after confirming the backend data is correct.
Resolution workflow
- Capture the affected lab name, user, node/device, and exact symptom.
- Compare the resource record with a known-good environment or backup when available.
- Run a small execution against the affected lab resource.
- Document any manual correction or support escalation in the change notes.
Last updated: October 8, 2026