|wrote on 16.09.20 at 13:58|
this is a known timing issue. To work around this, try to configure one schedule to stop at for example 11:00 and configure the next one to start at 11:01. That should do the trick.
|LG/Best regards, Alex|
"Journalism is printing what someone else does not want printed. Everything else is public relations."
- George Orwell