Automation Schedule run in our CI/CD pipeline is failing

Integrations
, , ,
1

Automation Schedule run in our CI/CD pipeline is failing with following error “Cannot execute this test suite collection. There is no Katalon Runtime Engine and TestCloud license available.”.

But Individual pipeline executions are running successfully. I have verified that licenses are available on the Katalon platform and have tried all the possible solutions within our CI/CD configuration. Need @KatalonSupport to resolve the issue

image
image376×155 7.68 KB

image
image881×189 11.4 KB

image
image1027×217 12.3 KB

image
image960×226 13.4 KB

2 Likes
2

Hi @sophia.n

From the screenshot you provided, it appears that your KRE license is assigned under a specific Organization. When running executions in CI/CD, KRE sometimes cannot correctly resolve which organization to use if the orgId parameter is not explicitly provided. This can lead to the error:

“Cannot execute this test suite collection. There is no Katalon Runtime Engine and TestCloud license available.”

Even though licenses are available on the platform.

Could you please try adding the organization ID parameter to your KRE command?

You can do this by adding -orgId right after the -apiKey parameter. The value should be the number portion from your organization ID (the part after OG-XXXXXXX). You can find it under My Account_01 in your screenshot.

Example:

-apiKey=xxxxx -orgId=XXXXXXX

After adding this parameter, please re-run the pipeline and see if the issue persists.

1 Like
3

hi @sophia.n

another thing worth checking is whether the scheduled job is triggering executions in parallel. Each parallel run consumes a KRE/TestCloud license, so if multiple jobs start at the same time (for example from a Test Suite Collection or overlapping schedules), you may still see this error even though licenses look available in TestOps.

It might help to check if other pipelines or scheduled runs are executing at the same time.

1 Like
4

@Slowey We have tried that way also. In our configurations we are adding
-apiKey=“$(api_key)” and then -orgID=“value”. Still we are receiving same error.

@depapp Currently we are executing Sequential for the scheduled run. and another run is not running at the scheduled time

Can anyone of you give another solutions to fix this issue?

1 Like
5

If the automation scheduled run in the CI/CD pipeline is failing, the issue is usually related to configuration, environment setup, or tool integration. When running automated tests through CI tools like Jenkins with test automation tools such as Katalon Studio, several factors should be checked.

  1. Review the pipeline execution logs. Most failures occur because the automation command cannot locate the project path, test suite, or execution profile. Ensuring that the correct command-line parameters are used for the automation execution is essential.
  2. Verify that the execution environment on the CI server is correctly configured. This includes checking browser drivers, Java versions, environment variables, and permissions. If the scheduled job runs on a different agent or container, some dependencies might be missing.
  3. Confirm that the test suite path and configuration settings are correct in the pipeline script. Sometimes pipelines fail simply because the test suite name or folder path has changed in the project repository.

Another important step is validating integration settings with external systems, such as test reporting or test management tools. For example, if the automation results are configured to sync with Katalon TestOps or an issue tracker like Jira, an expired API token or incorrect configuration may cause the job to fail.

6

@sophia.n since you are a paid user, did you reach out to dedicated katalon support via email or support portal?