Web-API commands fail at peak times

Having unreliable results from the nightmode setting at 22:00 in the evening I switched to sending a scheduled web-api lock action which also failed. The command is send succesfully (http response 204) but the lock action never reaches my SmartLock. However manual testing works fine.
At appears that 22:00 in the evening is just a bad time to schedule. 21:59 and 22:01 are fine and give no problem. Further testing learns that 06:00 and 07:00 in the morning and 20:00, 21:00 and 22:00 in the evening are bad times to schedule a command. ( probably a badly managed server overload ?)

Apparantly there is never a guarantee that a submitted Web-API command reaches the SmartLock and I think that’s worrying. You allways have to check the lock state afterwards.

Anyone else in the Nuki community experiencing this behaviour ?