# DB V2 - Revisit: bar chart to track daily number of starts stopped working with 1.30.0

**URL:** https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957
**Category:** Dashboard
**Tags:** dashboard-2
**Created:** [16 December 2025 11:21 UTC](https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957 "2025-12-16T11:21:24Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![houser](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/houser/32/57967_2.png) [@houser](https://discourse.nodered.org/u/houser)
#### Post date: [16 December 2025 11:21 UTC](https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957/1 "2025-12-16T11:21:24Z")

</div>

Dear @rakgupta  
Your excellent flow from August this year stopped working with the latest version of flow fuse dbv2,1.30.0  
I have tried to troubleshoot but it does not draw the bar charts anymore fr som reason and it is well beyond my skillset. It has worked perfectly until today and this update

If you have time and interest to revisit it or reopen the old thread about this it is here;

> [@DB V2 - bar chart to track daily number of starts?](https://discourse.nodered.org/t/db-v2-bar-chart-to-track-daily-number-of-starts/98688/58):
>
> Yes - the output is just one since it is triggered by a single “start”. However, the output contains the name of the machine and the count. You can modify the output (eg. turn it in todayCount.machne, todayCount.count) etc. and then use it the way you want to.

Many thanks regardless and best wishes for the holidays

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [16 December 2025 11:44 UTC](https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957/2 "2025-12-16T11:44:04Z")

</div>

There were several changes to the chart widget in this release. Are you sending timestamped data to the chart? If so, check what you have set for the x axis time limit in the chart config.  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/d/7dfbefb48b0750f42c24d3a951975889557fed19.png)

In previous versions the limit was not being applied correctly, now it is, so if you have that set to, for example, 1 hour, then data before that time will not be shown. If that is the problem you can either increase it or set it to zero, which will disable the time limit.

---

<div class="post-metadata">

### Author: ![houser](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/houser/32/57967_2.png) [@houser](https://discourse.nodered.org/u/houser)
#### Post date: [16 December 2025 11:58 UTC](https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957/3 "2025-12-16T11:58:04Z")

</div>

Many thanks for your reply! Understood. Will go through and do maintenance and checks..

---

<div class="post-metadata">

### Author: ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [16 December 2025 13:17 UTC](https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957/4 "2025-12-16T13:17:25Z")

</div>

Do you remember what version you were previously running?

---

<div class="post-metadata">

### Author: ![houser](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/houser/32/57967_2.png) [@houser](https://discourse.nodered.org/u/houser)
#### Post date: [16 December 2025 14:02 UTC](https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957/5 "2025-12-16T14:02:30Z")

</div>

I typically update to every version on this install, so whatever release came before 1.30.0.

Will check the flows more deeply as soon as there is time…could be something simple I guess. Will report back asap, just wanted to know if there is a known issue before I take it apart.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [16 December 2025 14:35 UTC](https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957/6 "2025-12-16T14:35:39Z")

</div>

Start by checking the x axis time limit as I suggested. I fully expect some to trip over that.

---

<div class="post-metadata">

### Author: ![houser](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/houser/32/57967_2.png) [@houser](https://discourse.nodered.org/u/houser)
#### Post date: [16 December 2025 15:08 UTC](https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957/7 "2025-12-16T15:08:31Z")

</div>

On this install and this chart I have "last 24 hours".  
I may have found a more specific reason/issue with the last line in the function node called:  
"Add data with timestamp and limit array length"  
It can be set to:

`return {payload: datapoint, action: 'append'};`  
or  
`return {payload: datapoint, action: 'replace'};`

and the `replace` is what gives an empty chart in 1.30.0. I see the dot in the chart move but it does not draw anything. I want "replace" as I only want the last 24 hours in this particular chart. Maybe it will work with "append" now. Will test it.

It could be something in my code to clean up the drawing that messes with the timestamp. Will have to look at it more closely.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [16 December 2025 15:24 UTC](https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957/8 "2025-12-16T15:24:27Z")

</div>

> [@houser](#):
>
> `replace` is what gives an empty chart in 1.30.0. I see the dot in the chart move but it does not draw anything.

Does that message include a full set of data points for the 24 hours? Replace means clear the chart and use what is in this message. Append means add the data in this chart to whatever is already there. If you have the time range set to 24 hours then now it will always remove any data older than that, which is what did not previously work correctly.

---

<div class="post-metadata">

### Author: ![houser](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/houser/32/57967_2.png) [@houser](https://discourse.nodered.org/u/houser)
#### Post date: [16 December 2025 15:37 UTC](https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957/9 "2025-12-16T15:37:26Z")

</div>

Thanks again. Yes, it should contain the full set for the last 24 hours.  
I do not presently fully understand the new functionality but will spend time with it and figure it out. If I understand you correctly I may have used a kind of workaround that is no longer needed. We shall see. I appreciate the comments!

---

<div class="post-metadata">

### Author: ![houser](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/houser/32/57967_2.png) [@houser](https://discourse.nodered.org/u/houser)
#### Post date: [17 December 2025 18:22 UTC](https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957/10 "2025-12-17T18:22:22Z")

</div>

Hello @Colin  
Ok, to cut a long story short:  
I did not research this deeply but if I now simply set the function node mentioned earlier to `append` rather than `replace` it works as it should again. This did not work that way before the update.

It seems to me that this could be that the change you mentioned in the code now works as it should and my workaround with using `replace` was a temporary happy accident that worked until this change.  
Thanks again for your comments and best wishes for the holidays!

---

<div class="post-metadata">

### Author: ![rakgupta](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rakgupta/32/42535_2.png) [@rakgupta](https://discourse.nodered.org/u/rakgupta)
#### Post date: [29 December 2025 22:52 UTC](https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957/11 "2025-12-29T22:52:10Z")

</div>

@houser - just catching up on this message as I was traveling. I haven’t upgraded to 1.3.0 as yet. Glad you found a work around.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [28 January 2026 22:53 UTC](https://discourse.nodered.org/t/db-v2-revisit-bar-chart-to-track-daily-number-of-starts-stopped-working-with-1-30-0/99957/12 "2026-01-28T22:53:05Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
