Troubleshooting

The product opens on DR Testing, then returns to another tab

Version 5.5.3 should preserve the selected route after reload. Clear a stale browser cache, open the intended route again, and capture the browser console plus final URL if the problem repeats.

DR Testing appears to refresh while idle

DR Testing fetches when the view opens, filters are applied, the user refreshes, or a relevant action completes. Monitor can refresh periodically by design. Record the tab, time, network request, and selected cloud scope if an unexpected refresh continues.

A workload from another cluster appears

Confirm the selected cloud scope and cluster, then compare the target identity in the test panel. Kubernetes mutation is restricted to the configured home cluster unless the installed integration explicitly supports another path. Do not proceed if the identity is wrong.

No Monitor events appear

Widen the date range and select Apply.
Clear other filters.
Confirm the cloud audit source is enabled and readable by the controller.
Allow for provider log-delivery delay.
Check whether inventory is also incomplete; that can indicate a separate API or permission gap.

Licence activation fails

Remove leading or trailing spaces from the activation key.
Confirm outbound HTTPS to the configured licence service.
Confirm the installation ID matches the entitlement.
Confirm the system clock is correct.
Record licence state, reason, installation ID, and timestamp; do not send private credentials.

A test is blocked

Read the returned reason before retrying. Common causes include unenrolled scope, exhausted limits, an unavailable feature, protected namespace, wrong cluster, insufficient redundancy, unsupported target configuration, missing permissions, or an active lease on the same target.

Evidence cannot be opened

Confirm the URI belongs to the configured evidence store, the user can read it, the object exists under the retention policy, and the digest matches the History record.