Just had the same issue and found the solution for those, who use spring-boot starter and initiate camunda spring beans manually:
POM
... <dependency> <groupId>org.camunda.bpm</groupId> <artifactId>camunda-engine-plugin-connect</artifactId> </dependency> <dependency> <groupId>org.camunda.connect</groupId> <artifactId>camunda-connect-core</artifactId> </dependency> <dependency> <groupId>org.camunda.bpm.extension</groupId> <artifactId>camunda-bpm-mail-core</artifactId> <version>1.3.0</version> </dependency> ...
Bean configuration:
@Bean fun engineConfiguration( @Value("classpath:/processes/*.bpmn") deploymentResources: Array<Resource> ): SpringProcessEngineConfiguration { val configuration = SpringProcessEngineConfiguration() configuration.processEngineName = "engine" configuration.databaseSchemaUpdate = "true" configuration.isJobExecutorActivate = false configuration.dataSource = dataSource configuration.transactionManager = DataSourceTransactionManager(dataSource) configuration.deploymentResources = deploymentResources configuration.processEnginePlugins.add(ConnectProcessEnginePlugin()) // this one is important return configuration }