Lab Management

• Lab Management in AIQ
• Check AIQ Test Node Status
• Troubleshoot Lab Management Upgrade Issues

Lab Management in AIQ

Lab Management in AIQ

Lab Management helps organize the environments, devices, browsers, nodes, and resources used by AIQ tests. Keep lab entries accurate so scheduled executions can find the correct capacity and environment details.

Recommended guidance

• Use clear names for labs, nodes, devices, and environment groups.
• Record ownership, location, access requirements, and maintenance windows for shared resources.
• Keep device and node availability current so teams do not schedule work against unavailable capacity.
• Separate production-like, staging, and experimental resources when possible.
• Review permissions so only authorized users can change shared lab configuration.

Operational workflow

1. Create or update the lab entry with the correct resource details.
2. Assign nodes, devices, or environment resources to the right group.
3. Run a small validation test to confirm the resource can be selected and used.
4. Update lab notes after upgrades, device swaps, or network changes.

Last updated: October 8, 2026

Check AIQ Test Node Status

Last reviewed: September 30, 2026

Use this article to verify whether AIQ Test Nodes are online, healthy, and ready to execute scenarios.

What changed in this article

• Shortened the title and aligned it with AIQ Test Node terminology.
• Added checks for online status, assigned capacity, browser/runtime availability, recent heartbeat, node logs, and execution queue symptoms.
• Added troubleshooting guidance for distinguishing node availability from scenario-level failures.

Validation workflow

1. Check the Test Node list or admin view for online/offline status and recent heartbeat.
2. Confirm the node has the required browser, runtime, network access, and capacity for the target execution.
3. If a run fails, compare node logs and queue status before changing the scenario itself.

Review note: This page now gives a health-check workflow instead of only pointing at a UI location.

---

Last updated: September 30, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

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

1. Capture the affected lab name, user, node/device, and exact symptom.
2. Compare the resource record with a known-good environment or backup when available.
3. Run a small execution against the affected lab resource.
4. Document any manual correction or support escalation in the change notes.

Last updated: October 8, 2026