Katalon KRE problems after Katalon organization change

Integrations
,
1

Recently, Katalon has made some changes to the management of KRE and KSE licenses by adding a new element called the organization.
Everything was working correctly until last Saturday, when all the tests scheduled in GitHub Actions stopped working.

The error message is as follows:

”The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the ‘Billing & plans’ section in your settings”

image
image1347×243 38.7 KB

The connection bettween Github and Katalon is via API_KEY token

Anybody with the same Issue or can help.

Thanks in avance.

1 Like
2

you might check:

  • Your GitHub Actions workflow files to see if they reference organization-specific settings

  • Your Katalon account to verify the organization assignment for your KRE/KSE licenses

  • Whether your API tokens or authentication credentials need to be regenerated

Based on the documentation, your GitHub Actions workflow requires a Katalon API key to authenticate with your TestOps account. The error message you’re seeing (“The job was not started because recent account payments have failed or your spending limit needs to be increased”) suggests that the API key being used may not have the proper permissions or organization context after Katalon’s organizational changes.

Root Cause

The new organization element in KRE/KSE license management likely affects:

  1. API Key Scope: Your existing API key may not have access to the new organization structure
  2. License Assignment: Your KRE license may not be properly assigned to the organization that your GitHub Actions workflow is trying to use
  3. Authentication Context: The workflow may need to explicitly reference the organization when authenticating

Solution 1: Regenerate Your Katalon API Key (Recommended)

Since Katalon introduced organizational changes, your existing API key may not have the correct permissions for the new structure.

Steps:

  1. Sign in to Katalon TestOps Admin

  2. Navigate to your Profile settings

  3. Go to API Keys section

  4. Delete your old API key

  5. Generate a new API key - this will ensure it has the correct organizational context

  6. Copy the new API key

  7. Update your GitHub Actions secrets:

    • Go to your GitHub repository
    • Navigate to Settings → Secrets and variables → Actions
    • Update the secret with your new API key (e.g., KATALON_API_KEY)

  8. Update your GitHub Actions workflow file (.github/workflows/your-workflow.yml):

    - name: Katalon Studio GitHub Action
  uses: katalon-studio/katalon-studio-github-action@v4.0
  with:
    version: '${{ your_KRE_version }}'
    projectPath: '${{ github.workspace }}'
    args: '-noSplash -retry=0 -testSuitePath="Test Suites/Your Test Suite" -browserType="Chrome (headless)" -apiKey=${{ secrets.KATALON_API_KEY }} --config -webui.autoUpdateDrivers=true'

Source: Katalon Studio GitHub Action Documentation

Solution 2: Verify License Assignment to Organization

Ensure your KRE license is properly assigned to your organization:

Steps:

  1. Sign in to Katalon TestOps Admin
  2. Select your Account
  3. Select your Organization
  4. Go to License → KRE (Floating) tab
  5. Verify that:
    • You have Available Licenses (not 0)
    • Your license hasn’t expired
    • The organization is correctly assigned

If licenses are not showing, contact Katalon Support to verify the migration of your licenses to the new organization structure.

Source: Quick Guide for Administrators - License Management

Solution 3: Check GitHub Secrets Configuration

Ensure your GitHub Actions secrets are properly configured:

Steps:

  1. Go to your GitHub repository
  2. Navigate to Settings → Secrets and variables → Actions
  3. Verify that KATALON_API_KEY (or whatever you named it) is present
  4. If missing, add it with your new API key
  5. Ensure the secret name matches exactly in your workflow file

Recommended Next Steps

  1. First, regenerate your API key (Solution 1) - this is the most likely cause
  2. Then, verify your license assignment (Solution 2)
  3. Finally, test your GitHub Actions workflow
1 Like
3

Thanks @Monty_Bagati for your detailed response, we are going to check everything and .we will keep you informed.

2 Likes
4

hi @amartinezalf

this usually happens because of the new organization-based licensing katalon introduced

after the org change, KRE executions are billed at the Organization level, not the personal account anymore
even if your API_KEY is valid, the job will fail if:

  • The Organization has no active plan
  • The spending limit is reached
  • The API_KEY belongs to a user/org without billing access

Things to check:

  1. Log in to Katalon → switch to the correct Organization

  2. Go to Billing & Plans

    • Make sure there is an active plan
    • Check spending limit and payment status

  3. Regenerate the API_KEY from a user who belongs to that Organization

  4. Update the API_KEY in GitHub Actions

Once billing is correctly set at the Organization level, GitHub Actions should start working again.

5

Thanks for all of you for the responses.

I have checked what @Monty_Bagati said:

you might check:

image
image1831×251 27.2 KB

  • Whether your API tokens or authentication credentials need to be regenerated

    • YES I the API KEY was regenerated

But doesnt´s work with this configuration.

But after several hours of thinking about it I realised that I have never user an organization level, and I decided to remove the assigned dedicated license

And now with this configuration it works:

1 - With a regenerated Api Key and update it on Githup actions secrets

2 - With no dedicated assignation for the KRE License

image
image1836×210 14.9 KB

Thanks for your help

1 Like
6

Thanks @depapp for your anwser too, I really apreciate that.

1 Like
7

glad that we were able to help you