@HalD reported a similar issue with the recent hub firmware update kicking all of his virtual timers out of their loops. But I believe he just had to go back and re-initiate the initial trigger on his.
The 14 second threshold sounds like a different problem, though. What automation are you using to create that delay? Is it just the standard custom automation creator in the new V3 app? Or something else?
If it’s the custom automation creator, definitely report it to support, that sounds like an official feature bug. 