Current Behavior

FrankSender with as target an adapter in another configuration target="<other-configuration>/<adapter-name>". When having FrankSenders in multiple configurations, targetting adapters in different configurations, about half of them throw an error about not being able to find the target configuration. The targetted configurations seems to start up just fine. Between environments(Local Docker vs CI/CD Docker) it varies which configurations can't be found by FrankSenders. Also happens with a single FrankSender targetting a single other configuration's adapter.

Only clues I can see is that the situation seems to occur when the target configuration finishes loading after the one that has the FrankSender in it. Suspecting it might be a load order/load timing issue.

Expected Behavior

FrankSender should not validate target status before all configurations are loaded.

Environment Information

FF! 9.3.0-20251004.042332: Kik-Inzage-Api 1.2.0
Running on 819f87599fc1 using Apache Tomcat/10.1.46
Java Version: OpenJDK Runtime Environment (21.0.8+9-LTS)
Heap size: 306.5 MiB, total JVM memory: 368.0 MiB
Free memory: 61.5 MiB, max memory: 3.8 GiB
Free disk space: 974.8 GiB, total disk space: 1006.9 GiB
Up since: 2025-10-15 08:06:38 (58m), timezone: Etc/UTC

Steps To Reproduce

No response

Configuration

Input

No response

What database are you using?

No response

What browsers are you seeing the problem on?

No response

Relevant Log Output

Anything else?

No response