Troubleshooting
Find the message or symptom you see. Each entry says why it happens, what to check and how to fix it.
In short
On this page you can
- Find out why a run is missing from the Reports list.
- Fix greyed-out Export PDF, Share Report and AI Analyze buttons.
- Understand runs that stay Running or turn Disconnected.
- Solve PDF, email, screenshot, video and log problems.
- Turn the AI features back on when they are disabled.
How to use it
- Copy the exact message you see, or describe the symptom.
- Find it in the headings below: list, export, steps and media, AI, load tests.
- Read Why, then do the Check list in order.
- Apply the Fix; if it still fails, write to info@smartestqa.ai with the report ID.
Finding and opening runs#
My run is not in the listList
- Why
- The list starts on This week, so older runs are hidden; or a search or filter is still on; or it was a dry run, which never creates a report.
- Check
-
- The date range button: pick Last Week, This month or Custom Range. A run counts by the start of its first test case.
- The search box is empty and the filter icon is not highlighted (Report Status on All, no tags).
- The project in the top bar is the run’s project.
- You started a pipeline in Schedule, not a Dry Run in Automate. See the report record and the live log.
- Fix
- Widen the range and clear the filters, see Find a run. For a dry run, run the test in a pipeline.
“No reports found” / “Please select a project”List
- Why
- No run matches the date range, search and filters, or no project is selected.
- Fix
- Select a project in the top bar, then follow My run is not in the list. A new project has no reports until its first pipeline run.
“This report couldn’t be opened. It may have been deleted or belong to another project.”List
- Why
- The
/report/<id>link belongs to another project than the one selected in the top bar, you have no access to that project, or the run no longer exists. - Fix
- Switch to the run’s project and open the link again. If you have no access, ask an admin to grant it (roles). People outside the company need Share Report instead of a link.
“Preparing report...” closes and I am left on the listList
- Why
- The overlay waits at most 10 seconds for the run’s first results. The run may be queued, or its agent may be slow to start.
- Fix
- Wait: the run appears at the top of the list when it starts, and the list refreshes itself while it runs. If a queue banner shows, your run is waiting for a free server. See Right after you start a run.
A run says Running for hours, or turned DisconnectedRuns
- Why
- The runner stopped reporting: the agent went offline or to sleep, the machine restarted, or the runner crashed. After 2 hours without finishing, the run is shown as Disconnected and its open attempts count as failed.
- Check
-
- The agent is green in Test Agents.
- InSight › Execution › Run environment lists stuck runs.
- The last test case tab: which step was running last.
- Fix
- Stop the run if it still shows Running, bring the agent back online, and run the pipeline again. How the rule works: the 2-hour rule.
Status says Completed but the Result is 4/5Runs
- Why
- One attempt was Disconnected. Disconnected attempts count as failed in the chip but do not turn the run status to Failed.
- Fix
- Open the run; the Summary shows the test case as Failed. Rerun it. See Run status.
The list says Failed but the Summary says Passed with warningsRuns
- Why
- A test case failed and then passed on an automatic retry. The list counts every attempt, so one failed attempt makes the run Failed; the Summary judges each test case by its last attempt.
- Fix
- Nothing is broken. Treat the test case as flaky and look at why the first attempt failed. See Result chip.
“No running run was found to stop; it may have already finished.”Runs
- Why
- The run ended between the last refresh and your click.
- Fix
- Nothing to do. The row updates within seconds.
“Could not stop the run.”Runs
- Why
- The stop request did not reach the server, or the run belongs to another company’s project.
- Fix
- Refresh the list and try again. If the run keeps going, stop its agent; the run then turns Disconnected. See Stop a run.
Export, share and tags#
“Please wait for execution to complete” (Export PDF, Share Report, tags, AI Analyze greyed out)Export
- Why
- These actions need a finished run. A run counts as finished when SmartestQA has closed it, or 2 hours after it stopped moving.
- Fix
- Wait for the run to end. If it is stuck, see Running for hours.
“Error occurred while exporting PDF”Export
- Why
- The server could not build the PDF, for example because a run from another project was requested or a temporary error occurred.
- Fix
- Reload the report and click Export PDF again. Very large runs take longer; wait until Exporting ends. If it keeps failing, send the report ID to support.
“No test log ID found”Export
- Why
- The report had not finished loading when you clicked.
- Fix
- Wait for the loading bar to end, or reopen the report from the list.
“Invalid email address” / “Please enter a valid email address.”Share
- Why
- The address is not in the form
name@domain.tld, or contains spaces. The dialog takes one address. - Fix
- Correct the address. Send again for each further recipient. See Share a report.
“The email could not be sent. Please try again later…” / “Failed to send email. Please try again.”Share
- Why
- SmartestQA’s mail server did not accept the message at that moment.
- Fix
- Try again in a few minutes. Meanwhile use Export PDF and send the file yourself. If it persists, write to info@smartestqa.ai.
The recipient did not get the emailShare
- Check
- “Email sent successfully!” appeared; the address is right; the recipient’s spam folder; company mail filters for PDF attachments.
- Fix
- Ask the recipient to allow SmartestQA’s sender address, or send the exported PDF yourself.
Steps, logs, screenshots and video#
“No logs found for this execution”Steps
- Why
- The chosen attempt wrote no step rows: it failed before its first step (for example the browser or app did not start), or Skip Successful Logs was on and every step passed.
- Fix
- Pick another Run or Retry, read the Summary’s Last 5 Error Logs, and check Pipeline Preferences for Skip Successful Logs.
“No screenshot available” / “No screenshots available”Media
- Why
- Screenshot on Fail was on, so only failed steps were captured; the upload from the runner failed; or the image could not be loaded in your browser.
- Fix
- Check Pipeline Preferences. Turn Screenshot on Fail off in the pipeline if you need every step. Reload the page if images fail to load right after login.
No video, “Please wait for the test to complete” or “No screenshots found”Media
- Why
- The video is built from screenshots after the test case ends; it needs screenshots and Video Recording on in the pipeline. Mobile cloud videos come from the provider and appear only when it delivered one.
- Fix
- Wait for the run to finish and click Create Video. If the button is missing, Video Recording was off for that run. See Video.
“User Defined Parameters Not Available”Steps
- Why
- No step of this test case saved a value into a variable in this run.
- Fix
- Nothing to fix. If you expected values, check that the steps save to a variable. See variables.
Last 5 Error Logs says “No error logs” for a failed run, or View Logs shows “No log found”Logs
- Why
- These are server logs, kept for 5 days. Older runs have none. A failure inside a step is not a server error, so a failed run can still have none.
- Fix
- Read the failed step in its test case tab instead. See Last 5 Error Logs.
“Please fill in all required fields.” when creating a taskTasks
- Fix
- Fill in the name, priority, status and type. See Open a task.
“An error occurred while creating the task…”Tasks
- Fix
- Try again, or create the task on the Tasks page and paste the report link into it.
“There are no requests to convert in this report…” / “Could not create the API steps”Network
- Why
- Convert to API steps needs a Network step that ran in “List” mode (whole session). The second message means saving the new test case failed.
- Fix
- Change the Network step to List mode, run the pipeline again and retry. See Network report.
Device Metrics or Crashes is emptyMobile
- Why
- They come from SmartTest Device Farm sessions only.
- Fix
- Run on the Device Farm to get them. See Device Metrics and Crashes.
AI analysis#
“AI Analysis is disabled. Go to Project Panel → AI Capabilities → enable "AI Auto Failure Analysis".” / “Enable … in Project Panel → AI Options”AI
- Why
- Enable AI or AI Failure Analysis is off for the project.
- Fix
- An Admin turns both on in Project Panel › AI Options. See Settings.
“Analysis already completed. Results are shown below.”AI
- Why
- This attempt was already analyzed, by you, a teammate or the automatic analysis after the run. Steps cannot be re-analyzed.
- Fix
- Read the AI Failure Analysis card. To analyze again, run the pipeline again.
Every verdict is Unclassified, or the confidence is 0%AI
- Why
- The analysis request failed (0%), or neither the AI nor the message rules recognised the error (25%).
- Check
- The project’s AI account works: with Own Account, the provider key and model are valid.
- Fix
- Fix the AI settings and run the pipeline again. See AI confidence.
“AI analysis results could not be saved.”AI
- Why
- The verdicts were produced but could not be stored with the run. They are visible until you leave the tab.
- Fix
- Read or copy them now. Reopen the report later; if the notes are gone, the attempt can be analyzed again.
“AI or AI Report Feedback is turned off for this project. You can turn it on in Project Settings → AI Options.”AI
- Fix
- An Admin turns on Enable AI and AI Report Feedback in Project Panel › AI Options. See Settings.
“Available when the run is completed.”AI
- Fix
- Wait for the run to finish, then click Analyze with AI.
“No logs were found to review for this run.”AI
- Why
- The run has no step rows, for example every test case failed before its first step.
- Fix
- Fix the start problem (agent, start page, device) and run again.
“The AI could not produce a review right now…” / “AI analysis failed.”AI
- Why
- The AI provider did not answer or returned an unusable answer.
- Fix
- Click Re-analyze in a moment. If it keeps failing, check the project’s AI account and model.
“The AI returned no findings for this run…” / “The AI response was cut off before it finished…”AI
- Why
- The answer was empty or incomplete, often on very large runs.
- Fix
- Click Re-analyze. For very large runs, review smaller pipelines. Limits: FAQ › Limits.
Load tests#
“No JTL report uploaded for this run.” / “JTL upload failed.”Load
- Fix
- Use Upload JTL with a
.jtl,.xmlor.csvresults file from JMeter. Check the file is a complete results file. See JTL files.
“Error loading report.” / “PDF generation failed.”Load
- Fix
- Reload the report. If the JMeter PDF fails, use the report’s main Export PDF, which includes the JMeter section.
Didn’t find your answer?Write to support with your project name and what you see on screen.
info@smartestqa.ai