The counter does actually start before Octave services are all up and running thus the 0 & 1 missing. And there is no control on the Timer from Octave once it is running (except fo changing the period and disabling/enabling it)
This is why in 3.1 we are introducing custom Timers that can be started/reset whenever needed (https://docs.octave.dev/docs/timer-resources#using-the-timer)
With regards to “2 & 3”: if you look at the “Generated Date”, you will see that they differ by 5 seconds as expected. And “2, 3 and 4” were sent alltogether, this is why they have the same “CreationDate” (reception date in the Cloud Stream)
Additional note: as indicating during the monthly call, I have had confirmation that we will soon have a dedicated resource that switches to “True” when all Octave services are up and running. This will allow making it much easier to trigger “initialization” types of logics.