Module broadcast from Initialize MHL case not working

[shuttlefan]

My DisplayUI module starts ADSS_client, status logger modules. These are all singletons.
As needed, ADSS_client will start a cloneable Policy module to handle data.

I've put a log message in each of the module's INITIALIZE MHL case.

Following is the logger output as the status broadcasts are being received:
Initial Logger Message
1/16/2025 3:41:36 AM; ADSS_CLIENT; Initialized
1/16/2025 3:41:36 AM; DISPLAY UI; Initialized
1/16/2025 3:42:19 AM; ADSS_CLIENT; Created Policy Mod#1
1/16/2025 3:42:19 AM; POLICY 1; StartPolicyExecuted

I know POLICY 1 is running as I'm getting data and the StartPolicyExecuted (status sent from another Policy module MHL case)

So for some reason, the POLICY 1: initialized  message never got received. 

I even added a case for MOD DID INIT broadcast and that wasn't received either.

No idea why just those two broadcasts are not seen.  
What am I missing?

 ADSS_client starts a new policy module.  The two update VIs are to notify the other modules that a new Policy module started.

Sending the INITIALIZED message as the last thing

DisplayUI registration

 

Logger registration

[shuttlefan]

After some more digging around, it appears that my logger can get the broadcasts if I delay the broadcasts (1 or 2sec)
So something downstream of the module startup/synchronization is happening two secs before the Initialize case has completed.

Looking at the code comments, my understanding is as soon as it enters the INITIALIZE and the synch caller events runs, the module should already be good to send/receive broadcasts.  Having to force a stall in order to do this doesn't seem like is the solution.
The two other singleton modules don't have this behavior.  

anyone have an idea why this is?  

[FabiolaDelaCueva]

Nothing jumps at me as to why adding a 2-second wait would make this code work.

Looks like a good candidate for running Lumos to get more details on the sequence of events:

https://dqmh.org/product/lumos/

You could request a trial version of Lumos and run it to see if that gives you more clarity as to what may be happening.

[shuttlefan]

Interesting...by doing what was suggested (using the null broadcast events; moving the registrations in the EHL for each), now the logger doesn't see ANY of the Module Did Init broadcasts anymore.

So broadcasts when module started outside is seen

when the module start is moved inside the EHL, it gets lost.

rest of code still runs normal.  Just that any broadcasts from within the "initialize" MHL case is lost.

[FabiolaDelaCueva]

Could you share a simplified version of your code?