We have a problem that we are not able to solve ourselves.
When running a large number og test cases, after a while, all test cases are set to cancelled in the same second.
Here is a screenshot of how it looks under test-executions:
After 59 runs (from 01.11.22, 10:04:19 pm - 02.11.22 kl.10:04:19 pm, the 60th execution is cancelled seemingly without an error:
All remaining test cases are then cancelled within the same second 02.11.22, 10:16:13 pm. These are all cancelled without being assigned a robot, as can be seen by the first screenshot.
we have our domain and username in the set up of the robot
Is this happening always or frequently? Can you select a few of the cancelled test cases and execute that only and see whether test cases are executing if the total number of test cases are less?
This is happening consistently, but the number of cases it executes before cancellations varies slightly. Always between 50 and 70.
If we select less than 50 test-cases it executes fine.
Re-executing the cancelled iflows are not possible as they are not in a final state.
We have checked memory and CPU logs for both the server where the test cases are running, and for the orchestrator, and none of them are on maximum capacity in the relevant time frame.