The current update cycle is round 30sec, but you see the update each minute since the readable date. jamesdumay meaning should we look into adding second while running or something along the lines of https://codepen.io/seoh/pen/PPZYQy where you see the update every second.

jamesdumay we decided to use the format of the stop clock in case we are in a running job. If not changed within the next 12 hours I will implement as the linked version.

I think the component here is actually TimeDuration but in principle it's very similar to ReadableDate. I would suggest that you add another prop called updatePeriod which you can set to any number in millis. Default to 30000. Then just use that value instead of "30000" when calculating timePeriodMillis. Also probably need to shift that logic to _handleProps since the value of props.updatePeriod can change. And if you just want to kick this bug over to me that is fine too

that is not the problem, the problem is that the TimeDuration is using

const duration = moment.duration(millis).humanize();

a fixed format ATM which results in that you see no seconds (because of humanize). In running, however, you would be more interested in a format like we use in the hint

moment.duration(millis).format("M [mos], d [days], h[h], m[m], s[s]");

I can add the updatePeriod but as long we use .humanize() the min update is a minute, you will not see seconds.

Ah, good call. Sounds like if duration < 60000 millis that we should display the exact number of seconds, in addition to updating every second.

Yeah something along that lines, but IMO the https://codepen.io/seoh/pen/PPZYQy would do just fine. https://www.youtube.com/watch?v=9aA-1rqtQWs

James Dumay: "23 minutes 31 seconds"