Submit Help Request
Help Desk
Submit Help Request

Runs and schedules

Why Runs stall, never start, fire twice, or miss a Schedule.
  • Runs and schedules
  • Email testing
  • Elements and selectors
  • Notifications
  • Values
  • Devices and access
  • Recovering work
    • Runs and schedules
    • Email testing
    • Elements and selectors
    • Notifications
    • Values
    • Devices and access
    • Recovering work
  • Why didn't my scheduled run trigger?

    Open Settings > Schedules and check the schedule status first. A schedule only runs while its status is Active. Select Reload in the toolbar so you are looking at the latest schedule status. Open ...
  • Why is my run stuck or still spinning?

    Use Reload first. The run may have finished while the page is still showing an older status. Open the run. Select Reload in the toolbar. If the status still looks wrong, refresh the browser. ...
  • Why didn't my run start?

    Use Reload first. This checks whether the page is showing an older status. Open the run. Select Reload in the toolbar. If nothing changes, refresh the browser. Check whether any test case ha...
  • Why is only one test running at a time?

    Check your concurrency settings first. Extra tests wait as Queued until a free slot is available. That often looks like only one test is running. Open Settings > Runners and find Concurrency Limit...
  • Why did CI/CD start the same Run more than once?

    Each successful POST to the CI/CD hook starts a new Run. DoesQA does not merge duplicate pipeline calls. Unexpected test counts usually come from tags, recipes, or Flow Branches, not from a single ...
  • Why isn't my Run status updating?

    Use Reload first. Run History and Run detail update live, but a sleeping tab or a missed socket update can leave an older status on screen after the Run has finished. Open Runs in the main menu ...
DoesQA
—
  • Homepage
  • Docs
  • App Login
  • Submit Help Request