Installation and setup
"release version 25 not supported" when building a project
"release version 25 not supported" when building a project
Your project is building with an older Java version. Verify that Java 25 is active:Also check the Java version Maven is using:If either reports a version older than 25, update your
PATH or JAVA_HOME to point to a Java 25 installation.Server fails to start on port 8080
Server fails to start on port 8080
Another process is using port 8080. Either stop the other process, or configure the Agents server to use a different port:
"fetch failed" when using the CLI
"fetch failed" when using the CLI
The CLI cannot reach the Agents server. Verify the server is running:If the server is running on a non-default port, set the port in your environment:
Licensing
License activation fails
License activation fails
Check the following:
- Your machine has network access to the LicenseSpring service.
- Your system clock is accurate. License validation is time-sensitive.
- The license key is entered correctly, including hyphens.
"quota exceeded" during workflow execution
"quota exceeded" during workflow execution
Your license quota (measured in additional lines covered) has been reached. The current workflow completes its in-progress work but does not start new partitions.Check your remaining quota:Contact your Diffblue account manager to discuss increasing your quota.
Workflow execution
Workflow fails during initial validation
Workflow fails during initial validation
The workflow checks that your project builds and existing tests pass before generating new tests. If validation fails:
- Run
mvn compileto verify the project builds. - Run
mvn testto verify existing tests pass. - Fix any build or test failures, then re-run the workflow.
Tests are rolled back after generation
Tests are rolled back after generation
Agents validates every generated test by compiling and running it. Tests that fail validation are rolled back automatically. This is expected behaviour. The workflow summary shows how many tests were committed and how many were rolled back.A high rollback rate may indicate that the target code is difficult to test in isolation, or that the project has complex dependencies that affect test execution.
Cherry-pick conflicts reported
Cherry-pick conflicts reported
Agents generates tests in a temporary worktree and cherry-picks committed tests back to your branch. If you made changes to the same files while the workflow was running, cherry-pick conflicts can occur.Resolve conflicts using standard git conflict resolution. The workflow reports which commits had conflicts.