The AI tries to start execution and gets stuck in endless loop when it does not have any url to start execution. I started manual AI execution even when no url was provided to it, but it was not intelligent enough to understand that there is no application url to start execution. And it basically continued in same state for 2days 17 hours. [image]

DEFECT - In the Plans section, every item in ADO is shown as ‘Test Cases’ [image] When we open it, it shows correctly [image]

Recently updated feature doesn’t work properly [image] [image]

All widgets don’t work in sync with the interval filter, only few shows relevant analytical data onchanging the scope of the filter. [image]

Hi @nghi.phan : is the issue resolved ?

[image] Monty_Bagati: I am not able to add automated test case that flowed from katalon studio to Azure Repos and then in true platform and when i try to create a test suite and add that test case under that , it fails with 500 server error. pls note that my PAT has all the read and write access and i have checked it writes properly to ADO I have created a ticket here: https://katalon.atlassian.net/browse/KSR-11808

Ticket has been created: https://katalon.atlassian.net/browse/KSR-11808

I will share with you when we have more details. The tickets are for internal tracking. Thank you

ok , you shared the link so i thought it must be for us as well

Hi Monty, Thanks for the detailed report — the screenshot made this much faster to trace. Our team dug into it and the schedule behind those rows is configured as a manual test run. On a manual schedule the cron fires and creates the work item with your selected cases, then stops there and waits for an explicit start. So NOT_STARTED is accurate but badly worded: it means “waiting on a person,” not “the system tried and failed.” We checked both the 25 and 26 Jul entries and there’s no automation job, manual-execution record, or TestCloud execution behind either one. Nothing was attempted, so there’s no downstream failure to find. The “Temporary Test Suite” naming threw us off initially too. It’s just the persisted container for whichever manual cases were selected at schedule creation — not related to the run sitting idle. So either start it via Run now / Run with TestPak when you want it, or recreate the schedule as an automated run against a real test suite with an environment and agent if you want it unattended. Please let us know your take on this Bella

How to manage AI execution errors

Bug Report

Topic		Replies	Views
Execution Exception: Unable to execute test suite Web Testing katalon-studio	4	1458	March 30, 2022
Integration with Azure DevOps Test Plans (Pre-release) Miscellaneous new-doc-request	16	2831	April 9, 2022
Katalon project task in Azure pipeline is getting stuck at Upload Report phase Integrations integrations , azure	2	1039	July 28, 2022
How to use Katalon for Azure DevOps Miscellaneous new-doc-request	116	22210	November 10, 2023
Azure DevOps Katalon plugin - Execution Timeout errors Integrations integrations , azure , katalon-studio	3	1765	July 19, 2022

How to manage AI execution errors

Related topics