@princemaxwell
waitFetch
will be applied only to the very first broadcast notification. If you set waitFetch: 120000
, this sequence will happen (I’ll assume the calendar module is described before CX3 in config.js)
- the calendar module starts the parsing of calendars.
- CX3 module starts. Library is loaded and the DOM is prepared. It is now ready to receive the events.
- The first calendars might complete its fetching. then calendar module will broadcast the events at that moment.
- CX3 receive the first broadcasted events. Wait 120000ms(2 minute) from that moment to get other lazy broadcasting coming.
- Other calendars might be fetched. But some might still need to be completed.
- Anyway, after 120000ms from the first broadcast, CX3 will draw the events that have arrived till then. (It means the view of CX3 is shown for the first time after at least 2 minutes from the boot)
- Then after 10minutes(
refreshInterval
), CX3 will refresh again. Maybe until then, all calendars would have been fetched.(I hope.)
Anyway your log was showing the 1st calendar fetching as below;
[20.03.2024 15:28.57.729] [INFO] Calendar-Fetcher: Broadcasting 2 events from ...
And the 8th fetching ;
[20.03.2024 15:30.30.417] [INFO] Calendar-Fetcher: Broadcasting 12 events from ...
It takes 93 seconds to complete. So I think waitFetch: 120000
(120 seconds) would be enough; however, if there are still missing events, the possible reasons would be;
- It takes more than 120 seconds at that moment randomly to complete fetching of all calendars since first fetching,
- some calendars were too fast-fetched before CX3 was ready. so they were missed. (all modules are loaded and starts sequentially, so if you have certain number of modules, CX3 may not be ready until that moment.)
Of course, you can adjust the order of modules in config, assign needed values of waitFetch
and refreshInterval
to show the entire events properly on the first boot time.
But, my suggestion is,
Just leave them and do nothing.
After 10 minutes from the first bootup, everything will be OK. Your MM might be rebooted at midnight or in the morning on real-life usage. MM would stay turned on all day or for several days. So literally, nobody will care, even realize there had been some missing events on the bootup time. You don’t have to make an effort to solve this unworthy issue.