I am getting a strange oddity in IntelliJ (2026.2.3 using Gradle) when switching to camunda 8.10.3 java client (from 8.9.23).
Al of a sudden the autowire (or constructor) injection gets an IntelliJ-warning. The compilation works but a red squiggly line appears saying " Could not autowire. No beans of ‘CamundaClient’ type found.". I use plain constructor injection in my service, like so:
public CamundaService(CamundaClient camundaClient) {
this.camundaClient = camundaClient;
}
The IntelliJ CamundaClient autowire warning after upgrading to 8.10 is likely related to key changes in how the Spring Boot Starter is packaged and configured in that version. I found the following relevant resources:
Does this help? If not, can anyone from the community jump in? 
Hints: Use the Ask AI feature in Camunda’s documentation to chat with AI and get fast help. Report bugs and features in Camuda’s GitHub issue tracker. Trust the process. 
if it compiles and the app actually starts and injects, id treat this as intellij not seeing the auto config rather than a real missing bean. after a version bump that happens when gradle still has a mix, like the old starter sitting next to the new client, so check the dependency tree for both versions and do a full gradle reimport. if only one version shows up, invalidate caches and restart usually makes the red squiggle catch up.
IntelliJ-only warning, not a real bug. Two quick checks:
-
Run the app. If CamundaClient injects fine, it’s cosmetic. If it fails at startup, make sure camunda-spring-boot-starter (not just camunda-client-java) is on the classpath.
-
If it works, fix the IDE. Try File → Invalidate Caches and Restart, then reimport the Gradle project. If the squiggle stays, add @SuppressWarnings("SpringJavaInjectionPointsAutowiringInspection") on the constructor.