Like @crrdlx said, these tokens are distributed via bots... these bots run over history information on the blockchain. The history is an expensive process that runs in parallel to the normal block information of the blockchain (that gets recorded on the ledger available to anyone). This history is sort of an easy processed way of accessing information from the past without having to "replay" (read) all the blocks from the beginning to that exact position (to be certain of what happened is true).

Sometimes these nodes have hiccups or need to restart and then need to catch up...
The bots run on this history and hence will only "action" things once that history catches up.

It's all on the ledger... so, it's just a matter of catching up and doing what was requested... no problems.

It should actually be interpreted as a normal thing to happen for applications (the bot)... similar to when a game website goes "under maintenance" while it's trying to do something on the back end... it's the same here... the difference is that the front ends don't block you into that "under maintenance" page... and you just keep waiting until the website shows you what was already "digitally verified".

Not sure if I complicated or made it more clear @new.things and @josie2214.

😅 !LOL