[GH-ISSUE #774] [Bug]: Duplicate archive entry when Bambuddy restarts during active print #514

New issue

Closed

opened 2026-05-07 00:11:11 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-07 00:11:11 +02:00

Owner

Originally created by @leisegang on GitHub (Mar 20, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/774

Originally assigned to: @maziggy on GitHub.

Bug Description

I have this problem when i start at 19. mars 2026, 22:14 and it finishes at 20. mars 2026, 03:19. it is stored as 2 prints in the archive. It also adds double filament and so on.
This is making the stats wrong. and gives wrong data.

Expected Behavior

i expected it to not duplicate.

Steps to Reproduce

start a print before midnight
Finish after midnight

Printer Model

H2D

Bambuddy Version

0.2.2

Printer Firmware Version

01.03.00.00

Installation Method

Docker

Operating System

Docker

Relevant Logs / Support Package

bambuddy-support-20260320-164133.zip

Screenshots

No response

Additional Context

No response

Checklist

I have searched existing issues to ensure this bug hasn't already been reported
I am using the latest version of Bambuddy
My printer is set to LAN Only mode
My printer has Developer Mode enabled

Originally created by @leisegang on GitHub (Mar 20, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/774 Originally assigned to: @maziggy on GitHub. ### Bug Description I have this problem when i start at 19. mars 2026, 22:14 and it finishes at 20. mars 2026, 03:19. it is stored as 2 prints in the archive. It also adds double filament and so on. This is making the stats wrong. and gives wrong data. <img width="877" height="556" alt="Image" src="https://github.com/user-attachments/assets/9735c64b-972e-43c1-aa1a-70aa3f387321" /> ### Expected Behavior i expected it to not duplicate. ### Steps to Reproduce start a print before midnight Finish after midnight ### Printer Model H2D ### Bambuddy Version 0.2.2 ### Printer Firmware Version 01.03.00.00 ### Installation Method Docker ### Operating System Docker ### Relevant Logs / Support Package [bambuddy-support-20260320-164133.zip](https://github.com/user-attachments/files/26145073/bambuddy-support-20260320-164133.zip) ### Screenshots _No response_ ### Additional Context _No response_ ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode - [x] My printer has Developer Mode enabled

BreizhHardware

2026-05-07 00:11:11 +02:00

closed this issue
added the
wontfix
label

BreizhHardware commented

2026-05-07 00:11:11 +02:00

Author

Owner

@maziggy commented on GitHub (Mar 21, 2026):

I checked the logs and the root cause is a server restart during the print, not a midnight boundary issue:

2026-03-20 03:19:13 — Bambuddy starting (server restart)
2026-03-20 03:19:17 — PRINT START detected (duplicate — reconnect sees RUNNING state as new print)
2026-03-20 03:19:17 — Original archive 204 marked as cancelled (age 5h > 4h stale threshold)
2026-03-20 03:19:17 — New duplicate archive created
2026-03-20 03:37:02 — PRINT COMPLETE updates the duplicate archive

The print started at 22:14 on Mar 19, and when Bambuddy restarted at 03:19 on Mar 20 (5 hours later), it reconnected to the printer, saw gcode_state: RUNNING, and treated it as a brand new print — creating a duplicate archive entry.

In general, restarting Bambuddy during an active print can cause tracking issues like this. We're looking into making the restart recovery more robust, but for now I'd recommend avoiding restarts while prints are running.

You can safely delete the duplicate archive entry from the Archives page to fix your stats.

@maziggy commented on GitHub (Mar 21, 2026): I checked the logs and the root cause is a server restart during the print, not a midnight boundary issue: 2026-03-20 03:19:13 — Bambuddy starting (server restart) 2026-03-20 03:19:17 — PRINT START detected (duplicate — reconnect sees RUNNING state as new print) 2026-03-20 03:19:17 — Original archive 204 marked as cancelled (age 5h > 4h stale threshold) 2026-03-20 03:19:17 — New duplicate archive created 2026-03-20 03:37:02 — PRINT COMPLETE updates the duplicate archive The print started at 22:14 on Mar 19, and when Bambuddy restarted at 03:19 on Mar 20 (5 hours later), it reconnected to the printer, saw gcode_state: RUNNING, and treated it as a brand new print — creating a duplicate archive entry. In general, restarting Bambuddy during an active print can cause tracking issues like this. We're looking into making the restart recovery more robust, but for now I'd recommend avoiding restarts while prints are running. You can safely delete the duplicate archive entry from the Archives page to fix your stats.