- Docs
- Help
- Troubleshooting
Troubleshooting
Find the message or behaviour you see, grouped by area. Each row gives the usual cause in one line and links to the full entry with what to check and how to fix it.
In short
On this page you can
- Find a message or symptom by area, from sign-up to MCP.
- See the usual cause in one line before you open the full fix.
- Jump to the detailed Why / Check / Fix entry on the module’s page.
- Prepare the details support needs when a fix does not help.
How to use it
- Press Ctrl+F and type a few words of the exact message, or pick the area.
- Read the usual cause in the row that matches.
- Click the message to open the full entry and work through Check in order.
- Still stuck: write to info@smartestqa.ai with the details listed at the end of this page.
Start from your question#
Most common
Pick your area
Every module also has its own troubleshooting page with all of its messages; they are listed in All troubleshooting pages.
Sign-up, login and licence#
| Message or symptom | Usual cause |
|---|---|
| “Please use a corporate email address” | The address is on a free mail provider such as gmail.com or outlook.com. |
| “This email address / company name / phone number is already in use” | A colleague already signed the company up. |
| “Your Password Has Not Been Set Yet” | The password link from the sign-up email was not used yet. |
| “Link Has Expired” or “Invalid or expired token” | Password links last 24 hours, and only the newest one works. |
| “The email or password you entered is incorrect” | Wrong password, Caps Lock, or the company signs in with Active Directory. |
| “No Project Access” or “Please contact your administrator to access this feature.” | You are a User without this project, or the screen is for Admins. |
| “Company license limit has been reached” | A licence counter is used up; deleted items still count. |
| “Your license has expired. Please renew to continue using all features.” | The trial or the licence period ended; data stays readable. |
| “Your license is suspended. Please contact support.” | A renewal charge failed and is being retried. |
| “Sample project has already been created for this company.” | The sample project is created once per company. |
| “This project name has already been used in this company.” | Project names are unique in a company. |
| A user cannot sign in with Active Directory | Not in a mapped group, the directory is unreachable, or the user limit is reached. |
All: Quick Start troubleshooting, Company settings › Users.
Extension and recording#
Web recording#
| Message or symptom | Usual cause |
|---|---|
| “Smartest extension not found” / “Browser extension still not detected” | The extension is missing or off, or the SmartestQA tab was open before you installed it. |
| The Chrome Web Store opens instead of my app | The page got no answer from the extension within 1.2 seconds. |
| “Please select a Start Page URL.” / “No URL configured for environment” | No start page is selected, or it has no address for that environment. |
| I don’t see the Discover Your App button | It exists only in WEB projects. |
| “No actions found on this page.” | The page had not loaded, the session timed out, or the controls are drawn on a canvas. |
| “Screenshots could not be uploaded — check the CDN/session.” | Your SmartestQA session expired, or a proxy blocks the upload. |
| Many items under “AI could not find a unique locator” | Repeated controls, such as an Edit button on every row, look the same. |
| “No new step found. Please refresh the page.” | After recording, the editor waited 20 seconds and found no new steps. |
| Recorded steps went missing after I switched test case | The extension saves into the test case you started recording from. |
| The Record button is missing | The test case is a load-test scenario (JMeter or k6). |
Mobile and desktop capture, App Map#
| Message or symptom | Usual cause |
|---|---|
| “Make sure Appium Server is running on http://localhost:4723” / “Could not start the session” | Appium is not running, the agent is offline, or the device or app settings are wrong. |
| “No SmartTest-Desktop agent found” / “No agent is online” | The agent is not running on the machine with the desktop app. |
| Mobile or desktop steps I recorded are gone | Inspector steps are added to the editor only and need Save. |
| A page shows “Not on map” or left its module | The page was renamed or created after the last Update map. |
| Error appMapScreenshotLimit when adding a screenshot | A page can have at most 4 screenshots. |
| I can’t delete an action | You are not an Admin or its creator, or test cases still use it. |
All: Discover troubleshooting, Automate › Recording.
Agents and devices#
Test agents#
| Message or symptom | Usual cause |
|---|---|
| The agent stays grey (Offline) / “The following agent(s) are currently offline” | The client is not running, the computer slept, it uses another agent’s key, or a proxy blocks it. |
| “No agents found” | The list could not be loaded, or your session expired. |
| “An agent with this name already exists. Please try a different name” | Agent names are unique in the company, including colleagues’ agents. |
| “Local agents cannot be deleted” / “You are not authorized to delete this agent…” | Your Localhost agent is permanent; shared agents need an Admin or their creator. |
| The Install Via CLI command fails | Wrong shell on Windows, curl or unzip missing, or a proxy blocks the download. |
| “This agent is offline. Live performance appears when it connects.” | Live performance needs a connected agent that sends metrics. |
Appium and local devices#
| Message or symptom | Usual cause |
|---|---|
| “Appium server not found” / “Appium off” / “Appium not running” | Nothing answers on localhost:4723 on the agent’s computer. |
| A test fails with “Server Unreachable / ECONNREFUSED 127.0.0.1:4723” | The terminal running Appium was closed. |
| Installing Appium fails with ERR_REQUIRE_ESM | The installed Node.js is too old for the current Appium. |
| “No Android devices found” / “No iOS devices found (macOS agent required)” | No device of the project’s platform is connected; iOS needs an agent on a Mac. |
| “No devices found. Is the agent running on port 8000?…” | Mobile Config asked your agent for its devices and got no answer. |
| A desktop test stops with “session terminated / driver unreachable” | On Windows: Developer Mode is off, so WinAppDriver crashes. |
Device Farm#
| Message or symptom | Usual cause |
|---|---|
| “Run your mobile tests on real devices. This feature is not enabled on your account yet.” | Your company does not have the Device Farm right. |
| I only see Test Agents, without the other tabs | The selected project is a WEB project; device tabs are hidden. |
| A farm run does not start: “concurrent session limit reached”, “device busy”… | A licence limit, the platform, or no free device refused the run before it started. |
| “Connection failed” / “Could not start stream” on a live device | The device is busy with a test, or the node or agent is unreachable. |
| A device stays Busy | A session or run ended without releasing the device. |
| A node is Offline, or its devices show “Node offline” | The node stopped sending heartbeats: off, asleep, client stopped or network down. |
| “App Library is full — update an existing app or delete one to add a new app.” | Your company already has 30 apps. |
| “Only APK, AAB, IPA or simulator .zip files can be uploaded.” | The file is not a supported app build. |
All: Agent Pool & Device Farm troubleshooting.
Running tests and dry runs#
Starting a dry run#
| Message or symptom | Usual cause |
|---|---|
| “Please save the test case before running” | The test case has unsaved changes; a dry run runs the saved version. |
| “To perform a Dry Run, you need to have the Agent installed locally…” | You chose your agent, but none is registered for you. |
| “Your agent appears to be offline…” | Your agent is installed but closed, asleep or without network. |
| “The test server queue is full…” / “The test server is not reachable right now…” | Run on Server already has 20 runs waiting, or the server runner is unreachable. |
| “… code is empty for Python step(s): …. Dry Run was not started.” | A Python step has no code for the project’s engine. |
| “The test could not start — a step's code or IF/ELSE/END structure is invalid…” | A code step does not compile, or an IF has no END. |
Dry-run results#
| Message or symptom | Usual cause |
|---|---|
| My test ran but there is nothing in Report | It was a dry run; only pipeline runs write reports. |
| The tree icon did not change after a dry run | The icon shows the last pipeline run; dry runs never change it. |
| I can’t stop a dry run | Dry runs have no stop; closing the panel only closes the panel. |
| The live log says Disconnected | The panel lost its connection; the run itself may still be going. |
| “Screenshot expired (kept for 1 hour).” | Dry-run screenshots are deleted after one hour. |
| The dry run used only one data row | Dry runs use the first dataset row; iterating rows is a pipeline feature. |
| The test passes in a dry run but fails in a pipeline | Different parameter values, data row, run location, environment or data left by earlier cases. |
| An action’s locators changed after a dry run | Auto-heal found the control with a new locator and saved it for review. |
Steps that fail#
| Message or symptom | Usual cause |
|---|---|
| “Failed to click on "…": Element not found | Locator: …” | No locator matched in time, after 3 attempts and auto-heal. |
| Type added the text after the old value | Type does not clear the field; use Clear & Type. |
| The test typed {{name}} literally | No step, key or stored value provided that variable before this step. |
| An assertion fails although the values look the same | Text comparison is case-sensitive and does not trim spaces or line breaks. |
| The test went on after a failed Visibility Check | A failed Visibility Check marks the step failed but does not stop the test case. |
| The API step passed although the API returned 404 or 500 | Any HTTP answer counts as a completed call; check the status code. |
| “Timeout: No email with OTP found within … seconds” | No new, unread e-mail matched the filters in time. |
| “Could not connect to the database…” in a Database step | The database is not reachable from the machine running the test, or the login is wrong. |
| A mobile step can’t find its element (“… did not appear in time”) | The screen differs from the recording, or the element is off screen. |
| “… of … requests failed (…%). Top error: …” on a load step | At least one request failed; one is enough to fail the step. |
All: Automate › Dry runs, Step troubleshooting.
Building tests: requirements, test cases, saving#
Saving test cases#
| Message or symptom | Usual cause |
|---|---|
| The Save button is grey: “Enter a test case name at the top to enable Save” | The name in the editor header is empty. |
| “Cannot save yet” — “n issue(s) found” | Some steps have missing or invalid values; up to five are listed. |
| "<step>" → Timeout: 1-300 sn | A step’s timeout must be between 1 and 300 seconds. |
| “This key is already registered as a global parameter, please change the key value.” | Another test case already produces a global parameter with this key. |
| “Test case not be updated” | The server refused the save; this one message covers several causes. |
| Steps disappeared after a colleague saved | Test cases are not locked; the last Save wins. |
| A rename or locator change showed up in other test cases | A step’s name and locators belong to the shared action. |
| “Cannot Add Recursive Test Case” | The template would make a test case call itself. |
| “This scenario is a load test: only JMeter, k6 and API steps can be added.” | A load test lives in a test case of its own. |
Archive, folders and modules#
| Message or symptom | Usual cause |
|---|---|
| “Used as a template step in other test cases. Remove those steps first:” | Other test cases call this one as a template. |
| “You can only archive what you created…” | Users may archive only items they created, including everything inside a folder. |
| “Only an admin can archive a module…” | Archiving a module moves its folders in Analyze and Automate together. |
| A restored test case is missing from its pipeline | Archiving removed it from pipelines; restoring does not put it back. |
| A folder I created appeared as a module in App Map and Automate | A folder directly under the project folder is a module. |
| “This module can’t be deleted yet: its folders still hold n item(s)…” | A module folder is removed with its module, and only when empty. |
Requirements#
| Message or symptom | Usual cause |
|---|---|
| “Start Date cannot be in the future” / “Start Date cannot be after End Date” | Start Date must be today or earlier, and not after End Date. |
| Generate is greyed out: “Please save the main requirement first” | Sub-requirements are generated from a saved main requirement. |
| Add is greyed out: “Please select a Sub Requirement first.” | Test cases link to sub-requirements, not to the main requirement. |
| A sub-requirement disappeared after saving | It was removed in the list before the save, which deletes it for good. |
| “Pipeline created successfully!” but there is no new pipeline in Schedule | A pipeline needs a Start Page URL; without one only the test suite is created. |
| Test Health shows a sub-requirement as not covered although it has a test case | It counts only when a linked test checks a result and passed its last run. |
All: Automate troubleshooting, Analyze troubleshooting.
Schedule and pipelines#
Saving and starting#
Schedules, triggers and queues#
| Message or symptom | Usual cause |
|---|---|
| My scheduled run did not start | No Next run, an end date passed, an offline agent, or SmartestQA was unavailable at that minute. |
| My pipeline is not on Scheduled Runs | Its Period is Real-time, or the Period change was not saved. |
| It runs at the wrong hour | Schedules use the SmartestQA server’s clock. |
| “End Date cannot be more than 1 year from now” | Daily, Weekly and Monthly schedules end at most one year ahead. |
| “Expected 5 fields (got n): minute hour day month weekday” | The cron expression has the wrong number of fields or an invalid value. |
| “Trigger is disabled” / “Trigger could not start: …” | The webhook was called while the trigger is off, or the pipeline could not start. |
| Queue items fail, or stay Pending | The run failed after every retry, or no report appeared in time. |
During and after a run#
| Message or symptom | Usual cause |
|---|---|
| My run stays “Queued” | All server slots are busy; runs started by hand go first. |
| The run shows Disconnected | The agent slept or went offline, or the server running it was lost. |
| No report e-mail arrives | E-mail is off in this pipeline’s own settings, the mode skips green runs, or it went to spam. |
| Thread Count or Retry Count jumps back to a lower number | Thread Count cannot exceed your licence’s Max Thread Count; Retry Count stops at 5. |
| A pipeline still runs with the old value after I changed Test Management | A pipeline copies the project’s settings when it is created. |
| “Dataset name was not found in Data Source.” | A parameter is linked to a dataset that was renamed or deleted. |
| The CLI command is refused, or contains YOUR_API_KEY | The command has no real agent key, or the key was regenerated. |
All: Schedule troubleshooting.
Reports and InSight#
| Message or symptom | Usual cause |
|---|---|
| My run is not in the list | The list starts on This week, or a search or filter hides it. |
| “This report couldn’t be opened. It may have been deleted or belong to another project.” | The link belongs to another project than the one selected. |
| A run says Running for hours, or turned Disconnected | The runner stopped reporting: the agent went offline or to sleep. |
| Status says Completed but the Result is 4/5 | An attempt was Disconnected; it counts as failed. |
| The list says Failed but the Summary says Passed with warnings | A test case failed and then passed on an automatic retry. |
| “Please wait for execution to complete” | Export, share, tags and AI Analyze need a finished run. |
| “Error occurred while exporting PDF” | The server could not build the PDF. |
| The recipient did not get the report e-mail | Spam folder or a mail filter for PDF attachments. |
| “No logs found for this execution” | The attempt failed before its first step. |
| “No screenshot available” | Screenshot On Fail was on, so only failed steps were captured. |
| No video, or “Please wait for the test to complete” | The video is built from screenshots after the test case ends. |
| “No JTL report uploaded for this run.” | The load run has no JMeter results file yet. |
| “No runs in this period” (InSight) | No pipeline run, and no test case run on its own, started in the period. |
| I ran a pipeline but InSight shows the old numbers | InSight calculates when the tab opens and when you click Refresh. |
| InSight and Report show different numbers | They count different things: Report counts every attempt, retries included. |
| Scenarios pass but requirement coverage stays low | A sub-requirement counts only when a linked scenario checks a result and passed. |
All: Report troubleshooting, InSight troubleshooting.
Integrations#
| Message or symptom | Usual cause |
|---|---|
| I don’t see Integrations in the menu | Integrations are for company Admins only. |
| “Please test the connection before proceeding” | The Jira, Xray and Confluence wizards continue only after a successful test. |
| The card says Ready although the integration is set up | The catalogue shows Active only while the integration is switched on. |
| A saved token stops working after I changed the address | A saved token is never sent to a new address; enter it again. |
| Jira: “Authentication failed: …” or “Connection Error” | Jira refused the user and token. |
| A new task did not create a Jira issue | The integration or Send Tasks to Jira is off, or the issue type needs extra fields. |
| The Jira status does not change with the task status | No Jira transition matches the mapped status. |
| Azure DevOps: “Authentication failed: check the personal access token” | The token is wrong, expired or lacks a scope. |
| No Test Execution appears in Xray after a run | Executions are exported on request, not after every pipeline. |
| “No test case in this run is linked to Zephyr” | Results are written only for test cases that came from or were sent to Zephyr. |
| “Could not send report. Check reportsParentPageId setting.” | The report page could not be created under the chosen parent page. |
| No Slack or Teams message arrives after a pipeline | The integration is off, or the matching event switch is off. |
| “This is an old Office 365 connector URL…” | Microsoft retired those connectors; use a Workflows webhook. |
| WhatsApp: the test works but run messages never arrive | The test uses Meta’s hello_world template; run messages need SmartestQA’s templates. |
| My webhook receiver rejects the signature | The HMAC is computed over re-serialised JSON, or with an old secret. |
| “SmartestQA: trigger failed (HTTP …)” | SmartestQA refused to start the pipeline; the response says why. |
| The build fails with state DISCONNECTED | A test case stayed running for more than 2 hours. |
| “Authentication failed (401): check the API key” (Datadog or Dynatrace) | Wrong key, or a key from another Datadog site. |
| “IMAP connection failed: …” | A normal password instead of an app password, IMAP off, or the wrong server or port. |
All: Integrations troubleshooting.
Data sources and API requests#
Data Source#
| Message or symptom | Usual cause |
|---|---|
| “This key already exists. Please enter a different name.” | Key names are unique in the project, across all folders. |
| I can’t delete a key | Deleting keys, and folders that still hold keys, needs an Admin. |
| The eye icon to show an encrypted value is missing | Only the person who created an encrypted value can show it. |
| My key lost its value after I switched Encrypt off | The old secret is never sent to the screen, so an empty field was saved. |
| A step uses {{ds:…}} literally, or gets an empty value | No key has that name, or the key has no value. |
| The run ignores my _TEST key | The suffix is not upper case at the very end, or the step names the suffixed key. |
| A step types {{excel:users}}_email literally | The dataset or column name does not match. |
| “Asterisk (*) is not allowed…” | A SELECT must list explicit columns. |
| “Connection test failed: the database server could not be reached…” | Wrong host or port, or a firewall that does not accept SmartestQA. |
| Test Connection works, but the run cannot connect | Test Connection runs from the SmartestQA server; a run connects from where it executes. |
| “Could not resolve DB data source ' key ': …” | The key’s SQL query failed or returned no rows. |
API Requests#
| Message or symptom | Usual cause |
|---|---|
| “Invalid Postman collection format” | The file is not a Postman collection export. |
| “This looks like a Swagger UI page, not the JSON spec…” | The address is the documentation page, not the specification. |
| “The request timed out (30s). The target did not respond.” | Often a firewall that silently drops traffic from the SmartestQA server. |
| “Host not found. Please check the URL.” | A typo, or an internal host the SmartestQA server cannot resolve. |
| My Params rows are not in the request | Send uses only the query string in the URL; runs add the Params rows. |
| Works with Send, but the run gets 401 Unauthorized | The step uses Basic Auth or Inherit from parent; a run applies only Bearer Token. |
| I changed the request, but the test still sends the old one | Each API step keeps its own copy of the request. |
| “Unsupported HTTP method” | HEAD and OPTIONS can be saved, but runs support only GET, POST, PUT, PATCH and DELETE. |
| The API step fails with an SSL or certificate error | API steps always verify certificates; self-signed and expired ones fail. |
All: Data Source troubleshooting, API Requests troubleshooting.
AI, autonomous agents and MCP#
AI features#
| Message or symptom | Usual cause |
|---|---|
| AI buttons are disabled, or “AI is not enabled or API key is missing for this project.” | Enable AI or the feature’s switch is off, or the AI connection does not work. |
| An AI button is greyed out: “Enable ' … ' in Project Panel → AI Options” | The feature needs Enable AI and, for some features, its own switch. |
| “AI API key is not configured (provider=…)…” | AI is on, but the project’s AI account has no key. |
| AI Test Connection fails | The provider refused the request; the message says why. |
| “Selected model/provider does not support image analysis (vision).” | You attached screenshots, and the model cannot read images. |
| “PDF does not contain extractable text. It may be a scanned/image PDF.” | The PDF holds pictures of pages, not text. |
| “No actions found for this project. Please record actions first.” | The AI builds steps from recorded actions, and there are none. |
| “AI could only partially cover your request — missing actions for …” | Parts of the prompt have no recorded action and became AI steps. |
| “AI request limit reached. Please wait a moment and try again.” | The AI provider is rate-limiting, unreachable, or the model was retired. |
| Generate Steps replaced my steps | Generate Steps replaces the whole step list, name and description. |
| Every AI verdict is Unclassified, or the confidence is 0% | The analysis request failed, or no rule recognised the message. |
Autonomous agents#
| Message or symptom | Usual cause |
|---|---|
| The Install button of an agent is greyed out | The agent needs something the project does not have yet, such as a repository. |
| Run now is greyed out | The agent is paused, or it already has a run going. |
| A run shows Budget blocked | The agent’s spend today reached its Daily budget. |
| A step says DENIED | The tool is not ticked, or the user the agent runs as lacks the permission. |
| “Expected run did not arrive (…) — is Claude Desktop open?” | The agent runs in Claude Desktop, which did not ask for it in time. |
| “The proposal could not be applied; see the step output for details.” | The record changed since the run, or you lack the permission. |
MCP and AI assistants#
| Message or symptom | Usual cause |
|---|---|
| SmartestQA does not appear in Claude, or its tools are missing | The client did not reload, the extension is off, or the server could not start. |
| The install command stops: Node.js is missing or too old | The installer needs Node.js 18 or newer. |
| “This account has no password yet. Set one with the link in your email, then try again.” | The connector signs in with a password, and your account has none yet. |
| “Too many failed attempts. Please try again in 15 minutes.” | Ten failed sign-ins within 15 minutes pause sign-in from that address. |
| The assistant says the SmartestQA key was rejected (401) | Wrong key, its host was deleted, or the key belongs to another environment. |
| “not allowed for this account (403)” or ACCESS DENIED | Your user may not do this, or may not open this project. |
| The assistant reports STALE_PREVIEW | The preview was used, the records changed, or it is older than 30 minutes. |
| “this connection to … is read-only” | This install was set up read-only. |
| A scenario is BLOCKED | Its dry run was not green three times, so the assistant stops and asks you. |
All: Autonomous Agents troubleshooting, MCP troubleshooting, Report › AI analysis.
Maintain, tasks and deploys#
Auto-heal and conversions#
| Message or symptom | Usual cause |
|---|---|
| A step failed, but “Nothing waits for review” | The runner refused to repair, or the repair was not saved. |
| The test fails again after I rejected a repair | Expected: Reject puts the old, broken locators back. |
| The next run made the same repair again | The runner does not remember rejections; the old locator is still broken. |
| “not healed — the page itself returned HTTP …” | The app itself looked broken, so the step fails as a defect. |
| “no element with the same identity, and AI auto-heal is turned off” | No exact match, and Enable AI or Auto-Heal is off. |
| “AI is not sure enough (best … < 85)” | The AI found no single clear winner. |
| “This AI step cannot be saved as an action…” | The AI used a verb that has no action type. |
| “There are no requests to convert in this report…” | The Network step did not run in List mode. |
Tasks#
| Message or symptom | Usual cause |
|---|---|
| A pipeline run failed but no task appeared | Auto Task Creation is off in the pipeline’s own settings, or it was a dry run. |
| The same failure creates a new task every run | Each failed run creates its tasks; there is no duplicate check. |
| Tasks vanished from the board | An Admin renamed the status those tasks still carry. |
| The board or list is empty although tasks exist | A filter remembered in your browser still applies. |
| “'In Review' status is used in 4 task(s). Please change the status of these tasks first.” | A status can be deleted only when no task has it. |
Deploys & Repos#
| Message or symptom | Usual cause |
|---|---|
| CI ran but nothing appears; the chip still says No deploy received yet | The notify step failed or did not run, or the page was not refreshed. |
| HTTP 401 from the deploy webhook (invalid deploy token) | The token is missing, mistyped or was replaced. |
| A deploy stays Not tested although a pipeline ran | The run is outside the deploy’s window or in another environment. |
| The deploy token is not shown any more | A token is shown only once; generate a new one. |
All: Maintenance troubleshooting, Tasks troubleshooting, Deploys & Repos troubleshooting.
Settings and permissions#
Project Panel#
| Message or symptom | Usual cause |
|---|---|
| Project Panel is greyed out: “Please contact your administrator to access this feature.” | The Project Panel is for Admins. |
| “Please enter a valid URL (e.g., https://example.com)” | A start page address must start with http:// or https:// and have no spaces. |
| “A Start Page with this name already exists…” | Start page names and addresses are unique in the project. |
| “This URL is being used in other places…” | Test cases or pipelines start on this URL. |
| Thread Count goes back to a lower number | It cannot exceed your licence’s Max Thread Count. |
| Passed steps have no screenshot in pipeline reports | Screenshot On Fail is on. |
| The app under test shows English dates or the wrong time | The browser runs with Browser Locale en-US, or the default timezone. |
| I don’t see Selenium Settings (or Playwright Settings) | Only the selected engine’s section is shown, in WEB projects. |
| Save Configuration is greyed out: “Select at least 1 test device for AWS Device Farm” | The chosen device cloud needs at least one device. |
| “APK read failed” / “IPA read failed” | The file is empty, over 200 MB, or not a valid build. |
Company Settings and Logs#
| Message or symptom | Usual cause |
|---|---|
| Company Settings is greyed out | Company Settings is for Admins. |
| “The email must be a corporate email.” | New users need a work address, not a public webmail one. |
| “This email is already in use. Please try another one.” | The address already has an account, in your company or another one. |
| “Company license limit has been reached…” when adding a user | Every user ever created counts, deactivated ones too. |
| A new user did not get the password setup e-mail | A typo in the address, a spam folder, or a mail server holding new senders. |
| A User sees “No Project Access” | No project has been assigned to them yet. |
| “Cannot change the role of the last admin…” | At least one Admin must remain in the company. |
| Server runs stay in Waiting | Your company reached its Concurrent runs limit, or all its servers are busy. |
| Run on Server cannot reach our test environment | The firewall does not allow SmartestQA’s egress IPs. |
| I don’t see Billing | Billing is not shown for every licence, and only Admins see it. |
| “Default statuses cannot be deleted” | Open, In Progress, Resolved and Closed exist in every company. |
| Logs is greyed out: “Please contact your administrator to access this feature.” | The audit log is for Admins. |
| A change I expected is not in the audit log | Only changes are recorded; opening pages, searches and previews are not. |
| Some sent fields show *** | The field name looks like a secret, so its value is masked. |
All: Project settings troubleshooting, Company settings troubleshooting, Logs troubleshooting.
All troubleshooting pages#
Still stuck: what to send to support#
Write to info@smartestqa.ai. A complete first message saves a round trip:
- The exact message, copied, or a screenshot of it.
- The time it happened, and your time zone.
- The company and project name, and the project type (WEB, MOBILE or DESKTOP).
- The ID or link of what is affected: the test case ID, the report link (
/report/<id>), the pipeline name, or the agent run number. - Where it ran: Run on Server, which agent, or which device.
- What you already tried from the entry on this page.
Never send passwords
Do not put passwords, tokens or API keys in the message. Support never needs them. If a key was exposed, replace it instead.
Didn’t find your answer?Write to support with your project name and what you see on screen.
info@smartestqa.ai