If you cannot access the workspace
- Confirm that you are using the workspace sign-in link provided to your team.
- Check that your account has been invited to the correct project or workspace.
- Try the latest version of your browser and a fresh session.
- Note the time, page, and visible message before contacting support.
If the coverage needs changes
- Return to the source. Check the requirement, workflow, or acceptance signal the case came from.
- Mark the gap. Identify the missing state, actor, data condition, or expected result.
- Edit the case. Make the smallest change that makes the intent and result reviewable.
- Rerun deliberately. Keep the scope visible so the new result can be compared with the previous one.
If an execution is not connected
Confirm the target environment, selected scope, permissions, runner status, and required test data. Integration behavior is workspace-specific, so capture the configuration and handoff where the run stopped.
Separate setup from product behavior. A missing environment signal or permission can look like a failed test. Preserve the run context before changing the case.
If a run fails
Review the failure step, expected result, captured evidence, and environment status. Decide whether the next action is a product fix, a coverage update, a rerun, or a controlled exception.
How to get help
Share the workflow, the expected outcome, and the point where the result diverged. A QTXpert specialist will contact you by email to understand the situation and discuss the next step.