Forum Discussion
TommyTester
Occasional Contributor
We only have one self-hosted agent configured.
If I was to login to it and run several back to back projects using either TestComplete or TestExecute, I don't encounter the issue. Likewise for other machines that aren't configured as agents.
The problem only seems to arise on the third or fourth back to back run, when the run has been triggered from the pipeline.
Marsha_R
3 years agoModerator
I suggest contacting Support directly with this issue. Here's the link:
Related Content
- 12 years ago
Recent Discussions
- 20 hours ago