Yes, it looks like the resilience4j version that we are using is pretty out to date, BDK's client retry mechanic is building on resilience4j 1.7.1, and resilience4j changed the executeCheckSupplier
method signature, this is the cause of your problem.
As you can see this BDK3.0.RC is not an official release, we'd like to see the feedback on the test both internally and externally, we will update the resilience4j dependency version in a next RC release.
Meanwhile, you unfortunately have to stick with the default resilience4j version from BDK.
thank you very much for your report.
Please note that BDK is an open source project in github, we'd like to switch our support completly from this forum to github, so any open issues will be shared to the community, i would kindly suggest you to post any issues directly to github project next time, https://github.com/finos/symphony-bdk-java/issues.
This is now addressed in 3.0.0.RC4
https://github.com/finos/symphony-bdk-java/releases/tag/v3.0.0.RC4