Date & Time: every x min card not triggering?

I have made an advanced flow, supposed to trigger every 3 mins using one of the the Date&Time cards. As I observed unexpected behaviour I added a Mobile notification card immediatedly after the trigger. Results are as below, with an unexpected gap from 14:48 to 16:42, almost 2 hours.

The flow itself is simple and fairly short, and does not have other delay timers or so.

I noticed similar erroneous behaviour in another flow using the Modbus app, and there I added some 1 sec “wait” timers between Modbus commands. That made it work reliably.

I just now added some wait timers in this flow and see if it will consistently trigger. Btw I have an early 2018 old-skool Homey. I find this Homey behaviour extremely annoying, it appears not reliable even for the most basic of functions. No warning, nothing, it just does not appear to work as required.

Questions:

  1. Are there other users experiencing similar problems using Date&Time cards not triggering?
  2. Suggestions for root causes? Only for Advanced flows? Could it be max no of notifications or notification buffer or so - however this does not explain below.
  3. Suggestions for solutions?

Make sure the “blind” time is caused by the trigger, because maybe it’s caused by the notification card(s) you use (!).

Timeline- and push notifications can be subject to rate limits (without any warning) →
To catch this limit, in Advanced Flow you’d add a card to the error output of just one random Timeline card, and to one of each Push notification card type.
Log cards of the Simple Log app are great to use for this, and I use Signal and Telegram (as part of the CallmeBot WhatsApp, Signal, Telegram, Facebook messenger app) flow cards to report stuff.

No.
But I’m experiencing unpredictable flakiness in Sun cards of that department.

I’m having occasional issues with the execution.

For instance: when it’s 13:00, the relay turns ON.

When the relay is ON, it should turn OFF after a 20-minute delay