---
title: "Troubleshooting"
section: "Automate"
description: "Fixes for SmartestQA Automate: the test case tree and archive, saving, recording and adding steps, variables, dry runs and the live log, and the AI features."
url: https://docs.smartestqa.ai/en/automate-troubleshooting.html
audience: [customer, admin]
updated: 2026-11-08
keywords: "automate error problem fix save disabled test case not be updated please select a start page url cannot save yet duplicate keys dry run disabled agent offline server queue full appium archive template licence limit ai not enabled"
---
# Automate: 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**

- Look up an Automate message by its exact text.
- Find out why a save, recording or dry run was refused.
- Fix archive, permission and licence refusals.
- Solve AI generation errors.

**How to use it**

1. Search this page for the words of the message ( Ctrl + F ).
2. Open the entry and read Why .
3. Work through Check , then apply Fix .
4. Still stuck? Write to info@smartestqa.ai with the test case ID and the message.

## Test cases, folders and archive

### Problem: “Company license limit has been reached. The maximum allowed usage for this operation has been exceeded.” _(Licence)_

- **Why:** Your company’s licence can limit how many test cases you create, and your company has reached that limit. The counter counts creations; archiving or deleting does not lower it.
- **Check:** An Admin sees the licence and its usage limits in [Company Settings › Billing › License Details](https://docs.smartestqa.ai/en/company-settings-billing.html#licence-details).
- **Fix:** Reuse existing test cases, or ask your admin to extend the licence. See [“Company license limit has been reached”](https://docs.smartestqa.ai/en/quick-start-troubleshooting.html#fix-limit-reached).

### Problem: “Your license has expired. Please renew to continue using all features.” _(Licence)_

- **Why:** The trial or the licence period has ended. You can still open your test cases, but creating new ones fails.
- **Fix:** An admin renews the licence in [Company Settings › Billing](https://docs.smartestqa.ai/en/company-settings-billing.html). See [Licence expired](https://docs.smartestqa.ai/en/quick-start-troubleshooting.html#fix-license-expired).

### Problem: “Used as a template step in other test cases. Remove those steps first:” _(Archive)_

- **Why:** The test case, or a test case inside the folder, is a template that other test cases call. Archiving it would break them.
- **Check:** The list under the message, or the template’s [×n badge](https://docs.smartestqa.ai/en/automate-numbers.html#template-badge).
- **Fix:** In each listed test case, [remove](https://docs.smartestqa.ai/en/automate-editor.html#remove-step) the template step (or [replace](https://docs.smartestqa.ai/en/automate-editor.html#replace-action) it) and save. Then delete again.

### Problem: “You can only archive what you created, and this contains items created by other people. An admin can archive it.” _(Archive)_

- **Why:** Users may archive only items they created themselves, including everything inside a folder. The archive dialog lists who created what.
- **Fix:** Ask an [Admin](https://docs.smartestqa.ai/en/company-settings-roles.html), or archive only your own test cases one by one. See [Archive and restore](https://docs.smartestqa.ai/en/automate-test-cases.html#archive).

### Problem: “Only an admin can archive a module (it moves its folders in Analyze and Automate together).” _(Archive)_

- **Why:** A top-level folder is a [module](https://docs.smartestqa.ai/en/automate-test-cases.html#modules); archiving it also archives its [twin in Analyze](https://docs.smartestqa.ai/en/analyze-folders.html#archive) and moves its [App Map pages](https://docs.smartestqa.ai/en/discover-app-map.html#modules) to Unassigned.
- **Fix:** Ask an [Admin](https://docs.smartestqa.ai/en/company-settings-roles.html).

### Problem: “You are not authorized to delete. Only admin or the creator can delete this.” _(Archive)_

- **Fix:** Ask the creator or an [Admin](https://docs.smartestqa.ai/en/company-settings-roles.html) to delete it.

### Problem: “Only the person who archived it or an admin can restore it.” _(Archive)_

- **Fix:** Ask the person who archived it (shown in the [Archive](https://docs.smartestqa.ai/en/automate-test-cases.html#archive)) or an [Admin](https://docs.smartestqa.ai/en/company-settings-roles.html).

### Problem: A restored test case is missing from its pipeline _(Archive)_

- **Why:** Archiving removes a test case from pipelines and test suites, and restoring does not put it back (“removed from *n* pipeline(s); restoring does not put it back”).
- **Fix:** [Add it to its pipelines again in Schedule](https://docs.smartestqa.ai/en/schedule-create.html#add-content). Its [requirement links](https://docs.smartestqa.ai/en/analyze-test-cases.html) were kept.

### Problem: I can’t move a module into another folder: “Only an admin can move a module folder under another module, because it removes the module.” _(Folders)_

- **Why:** Moving a module under another folder removes the module from the [App Map](https://docs.smartestqa.ai/en/discover-app-map.html#modules) and moves its [Analyze twin](https://docs.smartestqa.ai/en/analyze-folders.html#move-rename) too.
- **Fix:** Ask an [Admin](https://docs.smartestqa.ai/en/company-settings-roles.html), who confirms “Make “*name*” a sub folder?”. See [Move test cases and folders](https://docs.smartestqa.ai/en/automate-test-cases.html#move).

### Problem: “A module with this name already exists” or “Module name is required.” _(Folders)_

- **Why:** Top-level folders are modules, and module names must be unique and not empty. The check includes the module’s [App Map](https://docs.smartestqa.ai/en/discover-app-map.html#modules) and [Analyze twins](https://docs.smartestqa.ai/en/analyze-folders.html#modules).
- **Fix:** Choose another name, or [put the folder inside an existing module](https://docs.smartestqa.ai/en/automate-test-cases.html#move).

### Problem: “A module folder is deleted together with its module (App Map or the folder's menu).” or “This module can't be deleted yet…” _(Folders)_

- **Why:** A module folder cannot be deleted on its own. Deleting the module from the [App Map](https://docs.smartestqa.ai/en/discover-app-map.html#modules) is refused while its folders in Analyze or Automate still hold items.
- **Fix:** As an [Admin](https://docs.smartestqa.ai/en/company-settings-roles.html), use **Delete** in the folder’s **Options** menu in Automate: the module and everything in it go to the [Archive](https://docs.smartestqa.ai/en/automate-test-cases.html#archive). Or [move the items out](https://docs.smartestqa.ai/en/automate-test-cases.html#move) first.

### Problem: The tree shows “Unnamed test case #1234” _(Tree)_

- **Why:** The test case was created with [**New Test Case**](https://docs.smartestqa.ai/en/automate-test-cases.html#create-test-case) but never named and saved.
- **Fix:** Open it, [type a name in the header](https://docs.smartestqa.ai/en/automate-test-cases.html#create-test-case) and click **Save**, or [archive it](https://docs.smartestqa.ai/en/automate-test-cases.html#archive).

### Problem: **New Manuel Case** is greyed out with “Coming soon” _(Tree)_

- **Why:** Creating new manual test cases is not available yet. Existing manual cases still open. See [Manual test cases](https://docs.smartestqa.ai/en/automate-test-cases.html#manual-cases).

### Problem: “The folder summary could not be loaded.” or “Condition coverage not measured” _(Tree)_

- **Why:** The summary could not be read, or the pages the tests use have no conditions yet because the App Map was never updated.
- **Fix:** Click the folder again. For coverage, run [Update map](https://docs.smartestqa.ai/en/discover-app-map.html#update-map) in Discover. See [Folder summary](https://docs.smartestqa.ai/en/automate-numbers.html#folder-summary-counts).

## Saving

### Problem: The Save button is grey: “Enter a test case name at the top to enable Save” _(Save)_

- **Why:** The name in the editor header is empty (it has a red border).
- **Fix:** Type a name. See [Create a test case](https://docs.smartestqa.ai/en/automate-test-cases.html#create-test-case).

### Problem: “Please select a Start Page URL.” _(Save)_

- **Why:** A web test case needs a start page, for saving and for recording.
- **Fix:** Pick one in the dialog that opens; Save or recording continues. No start page in the list? [Add one](https://docs.smartestqa.ai/en/quick-start-connect.html#start-page-url). See also [Quick Start](https://docs.smartestqa.ai/en/quick-start-troubleshooting.html#fix-start-url).

### Problem: “StartPageUrl configuration error. Please re-select the URL.” _(Save)_

- **Why:** The start page stored with the test case is not in the form the editor expects.
- **Fix:** [Pick the start page again](https://docs.smartestqa.ai/en/automate-editor.html#environment) in the dialog that opens, then save.

### Problem: “Please fill the following fields:” … Description _(Save)_

- **Why:** Name, description, and for web start page and environment, are required. The description is [written by AI](https://docs.smartestqa.ai/en/automate-ai.html#ai-descriptions) and read only; normally it copies the name until then. A test case created by an import, a script or [MCP](https://docs.smartestqa.ai/en/mcp.html) can have an empty description that you cannot type into.
- **Fix:** Change the name slightly and change it back: the description copies it. Fill any other field the message names. See [Save](https://docs.smartestqa.ai/en/automate-editor.html#save).

### Problem: “Cannot save yet” — “*n* issue(s) found” _(Save)_

- **Why:** Some steps have missing or invalid values. Up to five are listed as `"Step" → field: message`, for example “Code body cannot be empty”, “API URL is required”, “Please enter a prompt first.”, “SQL query cannot be empty.”, “Fill in the key and the JSON path, or remove this row”.
- **Fix:** Select each listed step and fix the field in [**Parameters List**](https://docs.smartestqa.ai/en/automate-editor.html#step-parameters). What each step type needs: [step reference](https://docs.smartestqa.ai/en/automate-steps.html).

### Problem: `"<step>" → Timeout: 1-300 sn` _(Save)_

- **Why:** A [step’s timeout](https://docs.smartestqa.ai/en/automate-steps-flow.html#timeouts) must be between 1 and 300 seconds.
- **Fix:** Enter a value from 1 to 300 seconds.

### Problem: “Duplicate keys found in step:” or “Names that produce a global parameter must be unique within the test case. Conflicts:” _(Save)_

- **Why:** One step uses the same parameter key twice, or two steps store a value under the same variable name.
- **Fix:** Rename one of them, for example `orderNo` and `orderNo2`, and [update the steps that read it](https://docs.smartestqa.ai/en/automate-steps-variables.html#pass-values). See [Steps that produce a variable](https://docs.smartestqa.ai/en/automate-test-data.html#produce-variables).

### Problem: “This key is already registered as a global parameter, please change the key value.” _(Save)_

- **Why:** Another test case already produces a [global parameter](https://docs.smartestqa.ai/en/automate-steps-variables.html#global-parameter) with this key.
- **Fix:** Use a more specific key (`checkoutOrderNo`), or [read the other test case’s value](https://docs.smartestqa.ai/en/automate-test-data.html#variable-scope) with `{{tc:<caseId>.name}}`.

### Problem: “Parameter key can only contain letters, digits and underscore” _(Save)_

- **Fix:** Remove spaces, dashes, dots and braces from the key: `order_no`, not `order-no` or `{{orderNo}}`.

### Problem: “Test case not be updated” _(Save)_

- **Why:** The server refused the save. This one message covers several causes.
- **Check:** 1. A load-test rule: JMeter or k6 steps mixed with browser steps. See [Load-test scenarios](https://docs.smartestqa.ai/en/automate-add-steps.html#load-test-scenario).
  2. A [template step](https://docs.smartestqa.ai/en/automate-add-steps.html#add-template) that would create a loop, or that calls a test case of another project.
  3. A [mail step](https://docs.smartestqa.ai/en/automate-steps-mail.html#add-mail-step) whose [mail integration](https://docs.smartestqa.ai/en/integrations-email.html) is missing or belongs to another project.
  4. Two mobile or desktop [Get Text, Get Attribute or Store Variable steps](https://docs.smartestqa.ai/en/automate-steps-mobile.html#data) using the same variable key.
  5. You [lost access to the project](https://docs.smartestqa.ai/en/company-settings-users.html#project-access), or your session expired.
- **Fix:** Fix the cause, then save again. If none applies, reload the page (your unsaved changes are lost) and repeat the change in smaller parts to find the step. Still failing: write to info@smartestqa.ai with the test case ID.

### Problem: “Test Case Parameters Changed” opens on Save, or “Some schedulers could not be updated” _(Save)_

- **Why:** You changed parameters of a test case that pipelines use; the dialog syncs them.
- **Fix:** See [Test Case Parameters Changed](https://docs.smartestqa.ai/en/automate-editor.html#sync-pipelines). For pipelines that could not be updated, open them in Schedule and [check their parameters](https://docs.smartestqa.ai/en/schedule-settings.html#pipeline-parameters).

### Problem: A rename or locator change showed up in other test cases _(Steps)_

- **Why:** A step’s name is its action’s name, and [Action Detail](https://docs.smartestqa.ai/en/automate-editor.html#action-detail) edits the shared action. Both change every test case that uses the action. Action Detail edits are saved at once.
- **Fix:** Change it back the same way. Next time check the [usage chip](https://docs.smartestqa.ai/en/automate-numbers.html#usage-chip) and use [**Save as Copy**](https://docs.smartestqa.ai/en/automate-editor.html#action-detail). See [Rename a step](https://docs.smartestqa.ai/en/automate-editor.html#rename-step).

### Problem: Replace Action cleared my values _(Steps)_

- **Why:** [**Replace Action**](https://docs.smartestqa.ai/en/automate-editor.html#replace-action) resets the step’s parameters, because the new action may need different ones.
- **Fix:** If you have not saved, [leave without saving](https://docs.smartestqa.ai/en/automate-editor.html#unsaved-changes) to get them back. Otherwise enter them again. See [Replace the action](https://docs.smartestqa.ai/en/automate-editor.html#replace-action).

### Problem: “Save as copy is not supported for Assertion, JMeter, API, and AI action types.” _(Steps)_

- **Why:** These step types (also k6, database and global parameter) have their own action per step already.
- **Fix:** Edit the step’s values in [**Parameters List**](https://docs.smartestqa.ai/en/automate-editor.html#step-parameters); the change affects only this step.

### Problem: Steps disappeared after a colleague saved _(Steps)_

- **Why:** Test cases are not locked. The last **Save** wins, with the step list of whoever saved last.
- **Check:** **History** in [Test Case Detail](https://docs.smartestqa.ai/en/automate-editor.html#test-case-detail) shows who saved when.
- **Fix:** Add the missing steps again. Agree who edits which test case. See [Two people editing](https://docs.smartestqa.ai/en/automate-editor.html#concurrent-edits).

### Problem: “Are you sure to exit without saving?” _(Save)_

- **Fix:** **Save and Exit** keeps your changes; **Exit without saving** drops them; **Cancel** stays. See [Leaving with unsaved changes](https://docs.smartestqa.ai/en/automate-editor.html#unsaved-changes).

### Problem: An environment is greyed out: “No URL defined for this environment” _(Environment)_

- **Fix:** Add the address for that environment to the start page in [Project Panel](https://docs.smartestqa.ai/en/project-settings-project.html#url-form), or pick another environment. See [Environment and start page](https://docs.smartestqa.ai/en/automate-editor.html#environment).

## Recording and adding steps

### Problem: “No URL configured for environment: *env*” _(Recording)_

- **Why:** The start page has no address for the test case’s environment.
- **Fix:** [Switch the environment chip](https://docs.smartestqa.ai/en/automate-editor.html#environment), or add the address in [Project Panel › Start Page URLs](https://docs.smartestqa.ai/en/project-settings-project.html#start-pages).

### Problem: The Chrome Web Store opens, or “Browser extension still not detected. Please make sure the Smartest extension is installed and enabled, then try again.” _(Recording)_

- **Why:** The page did not get an answer from the extension.
- **Fix:** [Install or enable the extension](https://docs.smartestqa.ai/en/quick-start-connect.html#install-extension), press `F5` on the SmartestQA tab and click **Record** again. See [Quick Start](https://docs.smartestqa.ai/en/quick-start-troubleshooting.html#fix-extension-not-detected).

### Problem: “No new step found. Please refresh the page.” _(Recording)_

- **Why:** After recording, the editor waited 20 seconds and found no new steps on the server. Either nothing was recorded, or saving took longer.
- **Fix:** Press `F5` and reopen the test case. If you had unsaved changes, save them first. If the steps are still missing, [record again](https://docs.smartestqa.ai/en/automate-add-steps.html#record-web) and check that you are logged in to SmartestQA in the same browser.

### Problem: “An error occurred while loading steps.” _(Recording)_

- **Fix:** Reload the page and reopen the test case: the recorded steps are already saved on the server.

### Problem: Recorded steps went missing after I switched test case _(Recording)_

- **Why:** The [extension saves into the test case you started from](https://docs.smartestqa.ai/en/automate-add-steps.html#record-web). The editor shows them only when that test case is open.
- **Fix:** Open the test case you recorded into.

### Problem: The Record button is missing _(Recording)_

- **Why:** The test case is a load-test scenario (JMeter or k6), where recording is hidden.
- **Fix:** Record in a separate test case. See [Load-test scenarios](https://docs.smartestqa.ai/en/automate-add-steps.html#load-test-scenario).

### Problem: Mobile or desktop steps I recorded are gone _(Recording)_

- **Why:** Inspector steps are added to the editor only (“*n* step(s) added to the test case. Don't forget to save.”) and were not saved.
- **Fix:** [Record again](https://docs.smartestqa.ai/en/automate-add-steps.html#record-mobile-desktop) and click **Save**. The actions themselves were created and are in [Discover’s Action List](https://docs.smartestqa.ai/en/discover-actions.html#action-list).

### Problem: “No SmartTest-Desktop agent found. Install and start the desktop app on the computer where the application runs.” _(Recording)_

- **Fix:** Install and start the agent on that computer ([Windows](https://docs.smartestqa.ai/en/agent-pool-local-setup.html#windows-desktop) or [macOS](https://docs.smartestqa.ai/en/agent-pool-local-setup.html#macos-desktop)) and wait until it is [online](https://docs.smartestqa.ai/en/agent-pool-numbers.html#agent-online). See [Install an agent](https://docs.smartestqa.ai/en/quick-start-connect.html#install-agent).

### Problem: “Cannot Add Recursive Test Case” _(Steps)_

- **Why:** Adding this template would make a test case call itself, directly or through another template.
- **Fix:** Use a different template, or split the shared steps into a new template both can use. See [Add a template](https://docs.smartestqa.ai/en/automate-add-steps.html#add-template).

### Problem: JMeter or k6 is disabled, or “This scenario is a load test: only JMeter, k6 and API steps can be added.” _(Steps)_

- **Why:** A load test lives in a test case of its own, with only JMeter, k6 and API steps.
- **Fix:** Create a separate test case for the load test. See [Load-test scenarios](https://docs.smartestqa.ai/en/automate-add-steps.html#load-test-scenario).

### Problem: The same step was added twice _(Steps)_

- **Why:** The [Action List](https://docs.smartestqa.ai/en/automate-add-steps.html#action-list) and [Template](https://docs.smartestqa.ai/en/automate-add-steps.html#add-template) dialogs stay open and each click adds a step, so a double click adds two.
- **Fix:** [Remove](https://docs.smartestqa.ai/en/automate-editor.html#remove-step) the extra step.

### Problem: “Failed to add step.”, “Failed to remove step.” or “No step was selected. Please select a step and try again.” _(Steps)_

- **Fix:** Click the step first, then try again. If it repeats, save, reload the page and retry.

### Problem: “Failed to update action” _(Steps)_

- **Why:** The action could not be saved from Action Detail.
- **Fix:** Check the action’s fields and try again, or edit it in [Discover](https://docs.smartestqa.ai/en/discover-actions.html#manual-action).

## Variables and data

### Problem: The test typed `{{name}}` literally _(Variables)_

- **Why:** No step produced the variable before this step, and no stored value or [data source key](https://docs.smartestqa.ai/en/data-source-variables.html) of that name exists. Unresolved variables are used as written.
- **Check:** The spelling (names are case-sensitive), that the producing step comes earlier and is [active](https://docs.smartestqa.ai/en/automate-editor.html#activate-deactivate), and that it passed in the [log](https://docs.smartestqa.ai/en/automate-dry-run.html#live-log).
- **Fix:** Fix the name or the step order. See [Where a variable gets its value](https://docs.smartestqa.ai/en/automate-test-data.html#resolution).

### Problem: A step used a value from an earlier run _(Variables)_

- **Why:** Values that steps produce are also [stored as global parameters](https://docs.smartestqa.ai/en/automate-steps-variables.html#scope). When the producing step did not run this time, the stored value from an earlier run was used.
- **Fix:** Make sure the producing step runs before it, and check its [log line](https://docs.smartestqa.ai/en/automate-dry-run.html#live-log). See [Where a variable gets its value](https://docs.smartestqa.ai/en/automate-test-data.html#resolution).

### Problem: The dry run used only one data row _(Variables)_

- **Why:** Dry runs use the first row of a [dataset](https://docs.smartestqa.ai/en/data-source-datasets.html#loop). Iterating over rows is a pipeline feature.
- **Fix:** [Set the execute count in the pipeline](https://docs.smartestqa.ai/en/schedule-settings.html#loop-dataset). See [Run a test case once per data row](https://docs.smartestqa.ai/en/automate-test-data.html#data-driven).

### Problem: “This parameter belongs to a later step and may not have a value yet” _(Variables)_

- **Fix:** [Move the producing step above this one](https://docs.smartestqa.ai/en/automate-editor.html#reorder), or pick another value. The same applies to “This parameter is produced by this step, so it has no value inside the step itself”.

## Dry runs and the live log

### Problem: I can’t start a dry run: “Please save the test case before running” _(Dry run)_

- **Why:** The test case has unsaved changes. A dry run runs the saved version.
- **Fix:** Click **Save**, then [**Dry Run**](https://docs.smartestqa.ai/en/automate-dry-run.html#start-dry-run).

### Problem: “… code is empty for Python step(s): …. Dry Run was not started.” _(Dry run)_

- **Why:** A Python step has no code for the engine the project uses ([Selenium or Playwright](https://docs.smartestqa.ai/en/project-settings-engines.html)).
- **Fix:** Write the code in [that engine’s tab of the step](https://docs.smartestqa.ai/en/automate-steps-code.html#add-code-step), or [deactivate the step](https://docs.smartestqa.ai/en/automate-editor.html#activate-deactivate).

### Problem: “To perform a Dry Run, you need to have the Agent installed locally and the WebSocket connection established…” _(Dry run)_

- **Why:** You chose to run on your agent, but there is no agent registered for you.
- **Fix:** [Install the agent](https://docs.smartestqa.ai/en/quick-start-connect.html#install-agent), or choose [**Run on Server**](https://docs.smartestqa.ai/en/quick-start-connect.html#agent) for a web test.

### Problem: “Your agent appears to be offline…” or “Your agent is offline. Start the agent app to use this option.” _(Dry run)_

- **Why:** Your agent is installed but not connected: closed, asleep or without network.
- **Fix:** Start the agent and wait for the green dot in [Device Farm › Test Agents](https://docs.smartestqa.ai/en/agent-pool-agents.html#agent-status). See [Agent offline](https://docs.smartestqa.ai/en/quick-start-troubleshooting.html#fix-agent-offline).

### Problem: “The test server queue is full. Please try again in a moment.” or “The test server is not reachable right now. Please try again later.” _(Dry run)_

- **Why:** Run on Server has 20 runs waiting already, or the server runner is not reachable.
- **Fix:** Try again in a minute, or [run on your agent](https://docs.smartestqa.ai/en/automate-dry-run.html#web-targets). See [Quick Start](https://docs.smartestqa.ai/en/quick-start-troubleshooting.html#fix-server-busy).

### Problem: “Failed to start test execution!” _(Dry run)_

- **Fix:** Save, reload the page and try again. If it repeats, try the [other run target](https://docs.smartestqa.ai/en/automate-dry-run.html#web-targets) and write to info@smartestqa.ai with the test case ID.

### Problem: “Appium server not found — Appium server must be running to execute mobile tests…” _(Dry run)_

- **Fix:** [Open a terminal on the computer with the device and run `appium`](https://docs.smartestqa.ai/en/agent-pool-troubleshooting.html#fix-appium-not-running), then start the dry run again. See [mobile capture problems](https://docs.smartestqa.ai/en/discover-troubleshooting.html#mobile-desktop-issues).

### Problem: “The test could not start — a step's code or IF/ELSE/END structure is invalid…” _(Dry run)_

- **Why:** A [code step](https://docs.smartestqa.ai/en/automate-steps-code.html) does not compile, or an [IF has no END](https://docs.smartestqa.ai/en/automate-steps-flow.html#if-else). No step was run.
- **Fix:** Check the code steps and their [IF / ELIF / ELSE / END order](https://docs.smartestqa.ai/en/automate-steps-code.html#conditions). See the [step reference](https://docs.smartestqa.ai/en/automate-steps.html).

### Problem: The live log says Disconnected _(Dry run)_

- **Why:** The panel lost its connection to the live log; the run itself may still be going.
- **Fix:** Check your network and wait. The live log of a run is [kept for 30 minutes](https://docs.smartestqa.ai/en/automate-dry-run.html#dry-run-limits). Run again if the panel does not recover.

### Problem: “Screenshot expired (kept for 1 hour).” or “Screenshot could not be loaded.” _(Dry run)_

- **Why:** Dry-run screenshots are deleted after one hour.
- **Fix:** Dry run again, or run the test case in a [pipeline](https://docs.smartestqa.ai/en/schedule-create.html#add-content) to keep [screenshots with the report](https://docs.smartestqa.ai/en/report-steps.html#screenshots).

### Problem: The tree icon did not change after a dry run _(Dry run)_

- **Why:** The icon shows the last **pipeline** run. Dry runs never change it, and they do not appear in [**Recent runs**](https://docs.smartestqa.ai/en/automate-editor.html#test-case-detail) or [Report](https://docs.smartestqa.ai/en/report.html).
- **Fix:** [Run the test case in a pipeline](https://docs.smartestqa.ai/en/schedule-runs.html#run-now). See [Status icon](https://docs.smartestqa.ai/en/automate-numbers.html#status-icon) and [Run modes](https://docs.smartestqa.ai/en/automate-dry-run.html#run-modes).

### Problem: I can’t stop a dry run _(Dry run)_

- **Why:** Dry runs have no stop. Closing the panel only closes the panel.
- **Fix:** Wait for it to end; the [live log](https://docs.smartestqa.ai/en/automate-dry-run.html#live-log) shows when it is **Completed**. For long tests, [deactivate the steps](https://docs.smartestqa.ai/en/automate-editor.html#activate-deactivate) you do not need while you work on one part.

### Problem: An action’s locators changed after a dry run _(Dry run)_

- **Why:** [Auto-heal](https://docs.smartestqa.ai/en/maintenance-how-healing-works.html) found the control with a new locator and wrote it to the action. A review was created.
- **Fix:** [Approve or reject the review in Maintenance](https://docs.smartestqa.ai/en/maintenance-auto-heal.html#review-a-repair); [rejecting restores the old locators](https://docs.smartestqa.ai/en/maintenance-auto-heal.html#reject). See [Diagnose a failed step](https://docs.smartestqa.ai/en/automate-dry-run.html#read-a-failure).

### Problem: The test passes in a dry run but fails in a pipeline _(Dry run)_

- **Check:** 1. The pipeline’s own [parameter values](https://docs.smartestqa.ai/en/schedule-settings.html#pipeline-parameters) for this test case.
  2. Which dataset row the [failing iteration](https://docs.smartestqa.ai/en/report-steps.html#runs-and-retries) used.
  3. [Where the pipeline runs](https://docs.smartestqa.ai/en/schedule-where.html): the server cannot reach systems inside your network.
  4. The [environment](https://docs.smartestqa.ai/en/schedule-where.html#environment), and [earlier test cases in the pipeline](https://docs.smartestqa.ai/en/schedule-create.html#run-order) that change the data.
- **Fix:** See [Run modes](https://docs.smartestqa.ai/en/automate-dry-run.html#run-modes).

## AI

### Problem: AI buttons are disabled, or “AI is not enabled or API key is missing for this project.” _(AI)_

- **Why:** [**Enable AI**](https://docs.smartestqa.ai/en/project-settings-ai.html#enable-ai) or [**AI Document Analysis**](https://docs.smartestqa.ai/en/project-settings-ai.html#what-each-switch-unlocks) is off, or the project has no working [AI connection](https://docs.smartestqa.ai/en/project-settings-ai.html#ai-account). The tooltip names the missing option. A message starting “AI API key is not configured” means the [key](https://docs.smartestqa.ai/en/project-settings-ai.html#own-account) is missing.
- **Fix:** An [Admin](https://docs.smartestqa.ai/en/company-settings-roles.html) turns them on and sets up the AI connection. See [Turn on AI](https://docs.smartestqa.ai/en/automate-ai.html#enable-ai).

### Problem: “No actions found for this project. Please record actions first.” or “No pages found — record actions first.” _(AI)_

- **Why:** The AI builds steps from recorded actions, and there are none (or none on the selected pages: “No actions found for the selected pages.”).
- **Fix:** [Record the flow once](https://docs.smartestqa.ai/en/automate-add-steps.html#record-web), or scan pages with [Discover Your App](https://docs.smartestqa.ai/en/discover-your-app.html).

### Problem: “AI could only partially cover your request — missing actions for …” _(AI)_

- **Why:** Some parts of your prompt have no recorded action; they became [AI steps](https://docs.smartestqa.ai/en/automate-steps-ai.html).
- **Fix:** [Record the missing controls](https://docs.smartestqa.ai/en/automate-add-steps.html#record-web) and generate again, or [replace the AI steps with actions](https://docs.smartestqa.ai/en/maintenance-ai-steps.html#convert). See [Generate from Prompt](https://docs.smartestqa.ai/en/automate-ai.html#generate-from-prompt).

### Problem: “AI could not produce any usable steps for this prompt…”, “AI returned no usable test cases…”, “AI produced no usable scenarios…” or “The AI could not produce a valid result…” _(AI)_

- **Fix:** Try again. Rephrase with more detail: the page, the data and the expected result. Make sure the pages involved have a [purpose in the App Map](https://docs.smartestqa.ai/en/discover-app-map.html#page-information).

### Problem: “Please enter a prompt first.” _(AI)_

- **Fix:** Type what the test should do before you click [**Generate Steps**](https://docs.smartestqa.ai/en/automate-ai.html#generate-from-prompt), or fill the prompt of the [AI step](https://docs.smartestqa.ai/en/automate-steps-ai.html#add-ai-step).

### Problem: Generate Steps replaced my steps _(AI)_

- **Why:** [**Generate Steps**](https://docs.smartestqa.ai/en/automate-ai.html#generate-from-prompt) replaces the whole step list, name and description in the editor.
- **Fix:** If you have not saved: leave the test case with **Exit without saving**. If you saved, the old steps are gone; rebuild them or [record again](https://docs.smartestqa.ai/en/automate-add-steps.html#record-web).

### Problem: Expand Scenarios moved my test case, or created a new module _(AI)_

- **Why:** **Create** puts the variations and the original in a new folder under the original’s folder. At the root that folder is a [module](https://docs.smartestqa.ai/en/automate-test-cases.html#modules).
- **Fix:** [Drag the test cases](https://docs.smartestqa.ai/en/automate-test-cases.html#move) where you want them and [archive the empty folder](https://docs.smartestqa.ai/en/automate-test-cases.html#archive). See [Expand Scenarios](https://docs.smartestqa.ai/en/automate-ai.html#expand-scenarios).

### Problem: “AI request limit reached. Please wait a moment and try again.”, “Could not reach the AI service…” or “The configured AI model is no longer available…” _(AI)_

- **Why:** The AI provider is rate-limiting requests, cannot be reached, or the configured model was withdrawn. “Expansion failed” and “Error saving expansion” are the general errors of Expand Scenarios.
- **Fix:** Wait a minute and try again. For a withdrawn model, an Admin picks another model in the [AI settings](https://docs.smartestqa.ai/en/project-settings-ai.html#own-account).

### Problem: The description only repeats the name _(AI)_

- **Why:** The AI has not written it yet: descriptions are written when someone runs Update map in the App Map.
- **Fix:** Run [Update map](https://docs.smartestqa.ai/en/discover-app-map.html#update-map) and apply. See [AI descriptions](https://docs.smartestqa.ai/en/automate-ai.html#ai-descriptions).
