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 a Schedule message by its exact text.
- Find why a run did not start, waits, or ended Disconnected.
- Fix Before/After phases that cannot run.
- Solve schedule, time zone and cron problems.
- Fix triggers and queue items that do not run.
How to use it
- Copy the message you see, or describe the symptom.
- Find the group: saving, run list, schedule, starting, agents, runs, data, triggers, licence.
- Read Why, do the Check steps, then the Fix.
- Still stuck? Write to info@smartestqa.ai with the pipeline ID and the time.
Creating and saving#
“Company license limit has been reached. The maximum allowed usage for this operation has been exceeded.”Licence
- Why
- Your company’s licence limits how many pipelines you can create, and that limit is used up. Every click on New Pipeline counts one, and deleting does not give it back.
- Fix
- Reuse an existing pipeline: change its run list instead of creating a new one. To get more, an Admin checks the licence in ConfigurationCompany SettingsBilling (Billing) or asks info@smartestqa.ai.
“An error occurred while creating a new pipeline.” / “Please select a project first”Create
- Why
- No project is selected, or SmartestQA could not create the record.
- Fix
- Select a project at the top of the app, then click New Pipeline once more. If it keeps failing, reload the page and write to info@smartestqa.ai with the time.
Save or Save & Execute is greyed out; “Required: Name, Start Page URL”; “Scheduler name is a required field.”Save
- Why
- A required field is missing. Hover the button: the tooltip names what is missing.
- Check
- Name is filled.
- Web: a start page is selected and has an address for the chosen Environment.
- Run on Your Agent: at least one agent is ticked.
- Desktop: the Run Environment is an agent.
- Daily, Weekly, Monthly: both dates set; Custom: a valid cron.
- Fix
- Complete the field named in the tooltip (Save and Save & Execute).
“The start page URL is required. If the URL is missing, you can add it on the Project Panel page.” / “Start Page Url is required”Save
- Why
- A web pipeline needs a start page, and the project may have none yet.
- Fix
- Use Manage URLs next to the start page field, or add one in ConfigurationProject PanelStart Page URLs (how). Then pick it and save.
“Pipeline update failed. Please try again later.”Save
- Why
- The save was refused or did not reach SmartestQA, for example after your session expired.
- Fix
- Copy anything you typed, reload the page, log in again if asked and save once more. If it repeats for one pipeline only, write to support with the pipeline ID.
Save shows a step error, or “"Step" → Timeout: 1-300 sn”Parameters
- Why
- A value in Pipeline Parameters breaks a step rule, for example a step timeout outside 1–300 seconds, or a value that refers to a missing data key (“Key not found”).
- Fix
- Open Pipeline Parameters, filter With a problem, correct the value or use Back to case default, then save.
“Are you sure to exit without saving?”Save
- Why
- You are leaving the pipeline page with changes not yet saved.
- Fix
- Save and Exit keeps them; leaving without saving drops them. Scheduled runs always use the last saved version.
“name could not be deleted”Delete
- Why
- Only Admins and the person who created a pipeline can delete it.
- Fix
- Ask an Admin or the creator (shown under the Save buttons). To stop it running meanwhile, set Period to Real-time (Pause a schedule).
Run list and phases#
“Before/After cases cannot run on their own. Add at least one Test case or change their phase (e.g. Setup/Teardown).”Phases
- Why
- Before and After run around each Test row. Your run list has Before or After rows but no Test row, so there is nothing to wrap. The pipeline saves, but the run is refused; the run list also shows “Before/After cases run only around Test cases…”. The same rule comes back from the server as “This pipeline has Before/After cases but no Test case…”, for example from CI/CD or a schedule.
- Check
- Hover each row: a row without a phase chip is a Test row.
- Sub-pipeline rows do not count as Test rows.
- Fix
- Add a test case as a Test row, or change the Before and After rows to Setup and Teardown if they should run once (Phases).
Run is greyed out: “Please add at least one test case or requirement before executing”Run list
- Why
- The run list is empty (“Nothing to run in this pipeline”).
- Fix
- Open the pipeline and use Add Test Case, Add Requirement or Add Pipeline, then save (Add content).
Add Requirement (or Add Test Case) is disabled; “Requirement and case cannot be used together in the same pipeline”Run list
- Why
- A pipeline runs either test cases or requirements. The tooltip says “Cannot add requirements when test cases are present. Remove test cases first.” or the reverse.
- Fix
- Make a second pipeline for the other kind, and if you want them together, add one to the other with Add Pipeline (Sub-pipelines).
“name is already added to this pipeline.”Run list
- Why
- A test case can be in a run list once.
- Fix
- To run it more often, set a repeat in Data & loop or loop it over a dataset.
A dragged row jumps back to another placeRun list
- Why
- Rows are grouped by phase: Setup, Before, Test, After, Teardown. A row dropped into another group returns to its own.
- Fix
- Change the row’s phase with its chip, or move it within its group (Run order).
Scheduling#
My scheduled run did not startSchedule
- Check
- Open Scheduled Runs. Is the pipeline there, with a Next run? If not, see the next entry.
- Did the end date pass (Ended)?
- Is Next run at the hour you expect? See wrong hour.
- Did it start but fail at once? Look in Report for a run at that time; a run with an offline agent or Before/After without Test fails to start.
- Was SmartestQA unavailable at that minute? Missed times are not made up (Missed runs).
- Is the run waiting for a server? Scheduled runs come after runs started by hand (Server queue).
- Fix
- Correct what you found and save. Start one run by hand with Run to confirm the pipeline works.
My pipeline is not on Scheduled RunsSchedule
- Why
- Its Period is Real-time, or the Period was changed but not saved, or filters hide it.
- Fix
- Open the pipeline, choose the Period, set the dates, click Save. On Scheduled Runs click Clear Filters.
It runs at the wrong hour, or the cron summary and Next run disagreeSchedule
- Why
- Schedules use the SmartestQA server’s clock. Your typed time is read as server time; the summary under the cron field uses your browser’s clock.
- Fix
- Read Next run on Scheduled Runs (your time), work out the difference and shift the time by it (Time zone).
“End Date cannot be more than 1 year from now”Schedule
- Why
- Daily, Weekly and Monthly schedules may end at most one year ahead.
- Fix
- Set an end date within a year and put a reminder to extend it. Save again before it passes.
“Start Date is required”, “End Date is required”, “End Date cannot be before Start Date”, “End date must be after start date.”, “Start date year must be between 2000 and 2036.”Schedule
- Why
- Every Period except Real-time needs both dates, the end after the start, and a sensible year (2000 to ten years ahead).
- Fix
- Fill both date fields; check the year was not mistyped (Dates).
“Cron expression is required.”, “Expected 5 fields (got n): minute hour day month weekday”, “Invalid "x" for "field" (allowed: …)”Cron
- Why
- The expression is empty, has the wrong number of fields (6 or 7-field forms with seconds are not accepted here), or a value is out of range, such as minute 70 or hour 24.
- Fix
- Use five fields: minute 0–59, hour 0–23, day 1–31, month 1–12, weekday 0–7. Allowed forms:
*,*/n,n-m,n,m,n/step. Examples: Cron expressions.
A cron with a day and a weekday runs on the wrong daysCron
- Why
- When both day of month and weekday are set, only the weekday is used.
- Fix
- Set one of them to
*. For “the first Monday”, run every Monday and let the first test case check the date.
Starting a run#
“Pipeline execution failed. Check your environment and pipeline configurations.”Run
- Why
- SmartestQA could not hand the run over: the test server did not accept it (busy or not reachable), or the pipeline’s configuration is incomplete.
- Check
- Run Environment, start page and environment are set and saved.
- The test cases still exist.
- Try again in a minute: a busy server frees up.
- Fix
- Fix the configuration and run again, or switch to Run on Your Agent for now. If it persists, write to info@smartestqa.ai with the pipeline ID and the time.
“Name is required”, “Environment is required”, “Run Environment is required” when I click RunRun
- Why
- The saved pipeline misses a field that the list’s Run checks.
- Fix
- Open the pipeline, fill the field, save, and run again.
“Fix the values marked on the JMeter Settings tab first.”Load test
- Fix
- Open the JMeter Settings (or k6 / Load Test Settings) tab, correct the marked values, then save or run.
“Load test on PRP?”Load test
- Why
- The pipeline contains a JMeter load test and you chose PRP: it would load the live system.
- Fix
- Confirm only if load on production has been agreed. Otherwise keep TEST (Environment).
Agents, servers and devices#
“The following agent(s) are currently offline: … Please ensure your agents are running before executing the pipeline.” / “No online agent found. Please start your agent first.”Agent
- Why
- A ticked agent is not connected: the program is closed, the computer sleeps, or no heartbeat arrived for 90 seconds.
- Check
- The dot next to the host in Test Agent List is red.
- The agent program runs on that computer with that host’s API key.
- A proxy or firewall does not block its connection.
- Fix
- Start the agent and wait for green (when an agent is online), or untick the offline host. For web apps reachable from the internet, choose Run on Server. For nightly runs use a machine that stays on. More: agent offline.
“Please select at least 1 host. You can go to the pipeline detail and select from the Run Environment section.”Agent
- Why
- Run on Your Agent is selected but no host is ticked, often because you have no agent host yet.
- Fix
- Tick a host in Test Agent List and save. No host listed? Install an agent.
“Selected host is not accessible. Please go to the pipeline detail, select a valid host from the Run Environment section, and don't forget to save.”Agent
- Why
- A ticked host is not one you may use, typically a colleague’s personal agent in a pipeline someone else built.
- Fix
- Open the pipeline, untick that host, tick your own or a shared host, and save. Access to shared hosts is managed in Device Farm › Test Agents.
“The selected host could not be found. Please refresh and try again.”Agent
- Fix
- The host was removed. Reload the page, tick an existing host and save.
“Desktop tests run only on an agent (Windows or macOS) where the application and Appium are installed. Select at least one online agent.”Desktop
- Why
- Desktop pipelines cannot run on the server. The message names Windows, but agents on macOS run desktop pipelines too.
- Fix
- Open the pipeline (it switches to Run on Your Agent), tick an online agent on the machine with the application and Appium (Windows or macOS) and save (Desktop).
“Select an app for every selected target platform — Mobile Settings → SmartTest Device Farm”Mobile
- Fix
- Open the Mobile Settings tab, pick an app for each ticked platform, or untick a platform in Target Platforms (Mobile).
“No server is open to your company yet.”Server
- Why
- A specific server lists only servers dedicated to your company or your own self-hosted ones. You have none.
- Fix
- Use Automatic (recommended). For a dedicated server, ask info@smartestqa.ai.
My run stays “Queued”Server
- Why
- All server slots are busy. Runs started by hand and sub-pipelines go first; scheduled and queue runs wait longer. A run pinned to A specific server waits for that server only.
- Check
- The message shows your company’s runs ahead and the pool’s used slots (how to read it).
- Fix
- Wait: a waiting run never times out. Or Remove from queue and run on your agent. If your company often waits, ask an Admin to check Company Settings › Network & capacity and talk to support about capacity.
An environment is greyed out: “No URL defined for this environment”Environment
- Why
- The selected start page has no address for DEV, TEST or PRP.
- Fix
- Click Manage URLs and add the address (Start page URLs), or pick another start page. A choice not saved yet shows “This URL has not been saved yet. It will be saved when you click Save.”
During and after a run#
The pipeline stays RunningRun
- Why
- A case is still going (long tests, load tests), or the machine running it stopped reporting.
- Check
- Open the run in Report: which case is running and when it last logged.
- Fix
- Use Stop run. A case that stops reporting becomes Disconnected on its own (when).
The run shows DisconnectedRun
- Why
- The agent went offline or slept, the server running it was lost, or a case hung with no update.
- Fix
- Check the agent or try Run on Server; run again. For nightly runs use an always-on machine. Rules: Disconnected.
“Could not stop the run.” / “No running run was found to stop; it may have already finished.”Stop
- Why
- The stop request did not get through, or the run had already ended.
- Fix
- Reload the list. If it still shows Running, click Stop run again. Remember the case that is running finishes first (Stop a run).
“No report records found for this pipeline” in HistoryHistory
- Why
- No run in the selected period (the default is This month), or the pipeline has never run. Dry runs from Automate are never listed.
- Fix
- Choose All in the date filter, or run the pipeline.
No report e-mail arrivesE-mail
- Check
- Email Notification is on in this pipeline’s Test Management tab, not only in the project.
- Mode is Always, or the run had a failure (On Failure).
- Email To is filled; separate addresses with
;. - The spam folder.
- The run came from a queue item: those send no e-mail.
- Fix
- Correct the settings and save (E-mail).
Thread Count or Retry Count jumps back to a lower numberSettings
The CLI command is refused, or contains YOUR_API_KEYCLI
- Why
- The command has no real key (you have no agent host), the key was regenerated, or your user cannot open that project.
- Fix
- Copy your host’s key with Copy API Key, put it in the command, and check the pipeline ID. Ask an Admin for project access if needed (CLI).
Parameters and data#
“This pipeline has no parameters that take a value. If you just added cases, save the pipeline first; their parameters appear here as columns.”Data
- Why
- Table (manual) needs inputs: values typed or selected by steps. New cases appear only after a save, and cases with no Type or Select step have none.
- Fix
- Save the pipeline and reopen Data & loop. If still empty, the cases have nothing to fill (inputs).
“Save the pipeline first to use a table.” / “No rows to run”Data
- Fix
- Click Save on the pipeline, then add rows. Run table needs at least one enabled row; Run remaining only needs a row whose last result was not a success.
“Dataset name was not found in Data Source.”Data
- Why
- A parameter is linked to a dataset that was renamed or deleted.
- Fix
- Link the parameter to an existing dataset column again, or restore the dataset in Data Source.
“Only fixed cells are read from this dataset (always the same row)…”Data
- Why
- The parameters point at single cells, so every repeat reads the same row.
- Fix
- Link to the column header instead of a cell, so each repeat moves to the next row (Loop over a dataset).
Triggers and queues#
“The target pipeline has no inputs yet.” / “The processing pipeline has no inputs…”RPA
- Why
- The pipeline has no Type or Select steps, or its latest cases were not saved yet. Inputs are created automatically from those steps; there is nothing to mark by hand.
- Fix
- Save the pipeline, check Pipeline Parameters lists values, then reopen the trigger or queue (Pipeline inputs).
“Trigger is disabled” / “Trigger could not start: …”RPA
- Why
- The webhook was called while the trigger is off, or the target pipeline could not start (the reason follows the colon, for example an offline agent).
- Fix
- Switch Enabled on; fix the reason given, then use Test › Fire once (Test a trigger).
The e-mail trigger does not fire, or “Test failed”RPA
- Check
- Check connection says “Connection OK” (server, port, SSL, user, password).
- The mail is unread and in the configured Folder.
- From contains and Subject contains match it.
- You waited one check interval (default 120 s).
- Last error on the trigger row.
- Fix
- Correct the filter or credentials. A mail that failed to fire stays unread and is tried again at the next check.
The file trigger does not fireRPA
- Check
- The Robot machine shows online.
- Folder path exists on that machine and File pattern matches the file.
- The file has stopped changing for Stable for (s).
- Subfolders need Include subfolders.
- Fix
- Start the agent on the robot machine, correct the path or pattern, and drop the file again.
“Please fill in the required fields” when saving a trigger or queueRPA
- Fix
- Fields marked Required are empty: name, type, target, and the settings of the chosen type (for e-mail: server, user, password).
Queue items fail, or stay PendingRPA
- Why
- Failed: the run failed after every retry, no report appeared within 120 minutes (for example the agent was offline), or the run took more than 8 hours. Pending: the queue is paused, Periodically waits for its interval, Max parallel items are already running, or runs wait for a server.
- Fix
- Open run on the item to see why it failed, fix the cause, then Retry. Resume a paused queue; raise Max parallel if your agents can take it (Work with items).
An item is rejected as a duplicateRPA
- Why
- The queue has Unique reference on: “An item with an already queued reference is rejected”.
- Fix
- Use a different reference, or let the queued item finish first.
“The file has no data rows” / “v valid rows, e errors” on Excel importRPA
- Fix
- Start from Download template (.xlsx): the first row holds
referenceand the input names, one item per row below. The preview lists each error with its row and column; only valid rows are added with Add n to queue. A file can hold at most 5,000 rows; a bigger one is refused (in some versions in Turkish: “En fazla 5000 satır yüklenebilir”). Split it into several files.
The queue will not save with my interval (the message may appear in Turkish: “Aralık 1 dk ile 7 gün arasında olmalı”)RPA
- Why
- Interval (min) must be between 1 minute and 7 days (10,080 minutes).
- Fix
- Enter a value in that range, or choose When items arrive.
Licence and access#
“Your license has expired. Please renew to continue using all features.”Licence
- Why
- The free trial or your company’s licence has ended. Your pipelines and reports stay, but new pipelines and runs are refused.
- Fix
- An Admin renews the licence in ConfigurationCompany SettingsBilling (Billing), or contacts info@smartestqa.ai (more).
“Pipelines could not be loaded.”, “Scheduled runs could not be loaded.”, “Triggers could not be loaded”, “Queues could not be loaded”, “Items could not be loaded”Load
- Why
- The list could not be fetched: session expired, network trouble, or no access to the project.
- Fix
- Click Retry or Try Again. Still failing: reload the page and log in again. “No Project Access” means an Admin must give you access (access).
Didn’t find your answer?Write to support with your project name and what you see on screen.
info@smartestqa.ai