[GH-ISSUE #972] [Bug Report] It still doesn't load large files correctly in the Files tab. After the print fi

BreizhHardware commented

2026-05-06 12:31:51 +02:00

Owner

Originally created by @maziggy on GitHub (Apr 14, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/972

Originally assigned to: @maziggy on GitHub.

It still doesn't load large files correctly in the Files tab.
After the print finishes, it does not load the photo, filament data, cost, etc. in the Files tab.
In the Network tab, the FTP settings are as follows:

Enable Retry: ON
Retry attempts: 10 times
Retry delay: 30 secs
Connection timeout: 300 secs

Screenshot

System Information

{
  "generated_at": "2026-04-14T07:19:00.468458",
  "app": {
    "version": "0.2.3b4",
    "debug_mode": false
  },
  "system": {
    "platform": "Linux",
    "platform_release": "6.8.0-90-generic",
    "platform_version": "#91-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 18 14:14:30 UTC 2025",
    "architecture": "x86_64",
    "python_version": "3.13.13"
  },
  "environment": {
    "docker": true,
    "data_dir": "/app/data",
    "log_dir": "/app/logs",
    "timezone": ""
  },
  "database": {
    "archives_total": 172,
    "archives_completed": 153,
    "printers_total": 1,
    "filaments_total": 0,
    "projects_total": 0,
    "smart_plugs_total": 2
  },
  "printers": [
    {
      "index": 1,
      "model": "A1",
      "nozzle_count": 1,
      "is_active": true,
      "mqtt_connected": true,
      "state": "IDLE",
      "firmware_version": "01.07.02.00",
      "wifi_signal": -37,
      "reachable": true,
      "ams_unit_count": 1,
      "ams_tray_count": 4,
      "has_vt_tray": true,
      "external_camera_configured": false,
      "plate_detection_enabled": false,
      "hms_error_count": 0,
      "developer_mode": true,
      "nozzle_rack_count": 0
    }
  ],
  "settings": {
    "auth_enabled": "true",
    "setup_completed": "true",
    "auto_archive": "true",
    "save_thumbnails": "true",
    "capture_finish_photo": "true",
    "default_filament_cost": "15.0",
    "currency": "EUR",
    "energy_cost_per_kwh": "0.143",
    "energy_tracking_mode": "total",
    "check_updates": "true",
    "check_printer_firmware": "true",
    "include_beta_updates": "false",
    "notification_language": "en",
    "bed_cooled_threshold": "20.0",
    "ams_humidity_good": "40",
    "ams_humidity_fair": "60",
    "ams_temp_good": "28.0",
    "ams_temp_fair": "35.0",
    "ams_history_retention_days": "30",
    "per_printer_mapping_expanded": "false",
    "date_format": "eu",
    "time_format": "24h",
    "default_printer_id": "1",
    "ftp_retry_enabled": "true",
    "ftp_retry_count": "10",
    "ftp_retry_delay": "30",
    "ftp_timeout": "300",
    "mqtt_enabled": "false",
    "mqtt_broker": "",
    "mqtt_port": "1883",
    "mqtt_topic_prefix": "bambuddy",
    "mqtt_use_tls": "false",
    "ha_enabled": "true",
    "library_archive_mode": "always",
    "library_disk_warning_gb": "5.0",
    "camera_view_mode": "embedded",
    "preferred_slicer": "orcaslicer",
    "prometheus_enabled": "false",
    "dark_background": "oled",
    "dark_accent": "green",
    "dark_style": "glow",
    "debug_logging_enabled": "false",
    "debug_logging_enabled_at": "",
    "queue_drying_enabled": "false",
    "queue_drying_block": "false",
    "ambient_drying_enabled": "false",
    "drying_presets": "",
    "advanced_auth_enabled": "false",
    "smtp_auth_enabled": "true",
    "spoolman_enabled": "false",
    "spoolman_sync_mode": "auto",
    "spoolman_disable_weight_sync": "false",
    "spoolman_report_partial_usage": "true",
    "disable_filament_warnings": "false",
    "user_notifications_enabled": "true",
    "prefer_lowest_filament": "false",
    "default_bed_levelling": "true",
    "default_flow_cali": "false",
    "default_vibration_cali": "true",
    "default_layer_inspect": "false",
    "default_timelapse": "false",
    "stagger_group_size": "2",
    "stagger_interval_minutes": "5",
    "require_plate_clear": "true",
    "obico_enabled": "false",
    "obico_sensitivity": "medium",
    "obico_action": "notify",
    "obico_poll_interval": "10",
    "obico_enabled_printers": ""
  },
  "docker": {
    "container_memory_limit_bytes": null,
    "container_memory_limit_formatted": null,
    "network_mode_hint": "host"
  },
  "virtual_printers": [
    {
      "index": 1,
      "enabled": true,
      "mode": "proxy",
      "model": "N2S",
      "model_name": "A1",
      "has_target_printer": true,
      "has_bind_ip": true,
      "running": true,
      "pending_files": 0
    }
  ],
  "integrations": {
    "notification_providers": [
      {
        "type": "telegram",
        "enabled": true,
        "has_last_error": false
      }
    ],
    "spoolman": {
      "enabled": false,
      "reachable": false
    },
    "mqtt_relay": {
      "enabled": false,
      "connected": false,
      "broker": "",
      "port": 0,
      "topic_prefix": "bambuddy"
    },
    "homeassistant": {
      "enabled": true
    }
  },
  "database_health": {
    "backend": "sqlite",
    "journal_mode": "wal",
    "quick_check": "ok",
    "db_size_bytes": 2490368,
    "wal_size_bytes": 4169472
  },
  "dependencies": {
    "fastapi": "0.135.3",
    "uvicorn": "0.44.0",
    "pydantic": "2.13.0",
    "sqlalchemy": "2.0.49",
    "paho-mqtt": "2.1.0",
    "psutil": "7.2.2",
    "httpx": "0.28.1",
    "aiofiles": "25.1.0",
    "cryptography": "46.0.7",
    "opencv-python-headless": "4.13.0.92",
    "numpy": "2.4.4"
  },
  "log_file": {
    "size_bytes": 122018,
    "size_formatted": "119.2 KB"
  },
  "network": {
    "interface_count": 2,
    "interfaces": [
      {
        "name": "enp2s0",
        "subnet": "x.x.1.0/24"
      },
      {
        "name": "macvlan-shim",
        "subnet": "x.x.1.0/24"
      }
    ]
  },
  "websockets": {
    "active_connections": 1
  }
}

Logs (sanitized): bambuddy.log

Submitted via BamBuddy Bug Report

Originally created by @maziggy on GitHub (Apr 14, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/972 Originally assigned to: @maziggy on GitHub. It still doesn't load large files correctly in the Files tab. After the print finishes, it does not load the photo, filament data, cost, etc. in the Files tab. In the Network tab, the FTP settings are as follows: Enable Retry: ON Retry attempts: 10 times Retry delay: 30 secs Connection timeout: 300 secs ### Screenshot ![Bug Report Screenshot](https://raw.githubusercontent.com/maziggy/bambuddy/bug-report-assets/screenshots/f1b23b7cbdeb40ab9400864293666d5f.png) <details> <summary>System Information</summary> ```json { "generated_at": "2026-04-14T07:19:00.468458", "app": { "version": "0.2.3b4", "debug_mode": false }, "system": { "platform": "Linux", "platform_release": "6.8.0-90-generic", "platform_version": "#91-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 18 14:14:30 UTC 2025", "architecture": "x86_64", "python_version": "3.13.13" }, "environment": { "docker": true, "data_dir": "/app/data", "log_dir": "/app/logs", "timezone": "" }, "database": { "archives_total": 172, "archives_completed": 153, "printers_total": 1, "filaments_total": 0, "projects_total": 0, "smart_plugs_total": 2 }, "printers": [ { "index": 1, "model": "A1", "nozzle_count": 1, "is_active": true, "mqtt_connected": true, "state": "IDLE", "firmware_version": "01.07.02.00", "wifi_signal": -37, "reachable": true, "ams_unit_count": 1, "ams_tray_count": 4, "has_vt_tray": true, "external_camera_configured": false, "plate_detection_enabled": false, "hms_error_count": 0, "developer_mode": true, "nozzle_rack_count": 0 } ], "settings": { "auth_enabled": "true", "setup_completed": "true", "auto_archive": "true", "save_thumbnails": "true", "capture_finish_photo": "true", "default_filament_cost": "15.0", "currency": "EUR", "energy_cost_per_kwh": "0.143", "energy_tracking_mode": "total", "check_updates": "true", "check_printer_firmware": "true", "include_beta_updates": "false", "notification_language": "en", "bed_cooled_threshold": "20.0", "ams_humidity_good": "40", "ams_humidity_fair": "60", "ams_temp_good": "28.0", "ams_temp_fair": "35.0", "ams_history_retention_days": "30", "per_printer_mapping_expanded": "false", "date_format": "eu", "time_format": "24h", "default_printer_id": "1", "ftp_retry_enabled": "true", "ftp_retry_count": "10", "ftp_retry_delay": "30", "ftp_timeout": "300", "mqtt_enabled": "false", "mqtt_broker": "", "mqtt_port": "1883", "mqtt_topic_prefix": "bambuddy", "mqtt_use_tls": "false", "ha_enabled": "true", "library_archive_mode": "always", "library_disk_warning_gb": "5.0", "camera_view_mode": "embedded", "preferred_slicer": "orcaslicer", "prometheus_enabled": "false", "dark_background": "oled", "dark_accent": "green", "dark_style": "glow", "debug_logging_enabled": "false", "debug_logging_enabled_at": "", "queue_drying_enabled": "false", "queue_drying_block": "false", "ambient_drying_enabled": "false", "drying_presets": "", "advanced_auth_enabled": "false", "smtp_auth_enabled": "true", "spoolman_enabled": "false", "spoolman_sync_mode": "auto", "spoolman_disable_weight_sync": "false", "spoolman_report_partial_usage": "true", "disable_filament_warnings": "false", "user_notifications_enabled": "true", "prefer_lowest_filament": "false", "default_bed_levelling": "true", "default_flow_cali": "false", "default_vibration_cali": "true", "default_layer_inspect": "false", "default_timelapse": "false", "stagger_group_size": "2", "stagger_interval_minutes": "5", "require_plate_clear": "true", "obico_enabled": "false", "obico_sensitivity": "medium", "obico_action": "notify", "obico_poll_interval": "10", "obico_enabled_printers": "" }, "docker": { "container_memory_limit_bytes": null, "container_memory_limit_formatted": null, "network_mode_hint": "host" }, "virtual_printers": [ { "index": 1, "enabled": true, "mode": "proxy", "model": "N2S", "model_name": "A1", "has_target_printer": true, "has_bind_ip": true, "running": true, "pending_files": 0 } ], "integrations": { "notification_providers": [ { "type": "telegram", "enabled": true, "has_last_error": false } ], "spoolman": { "enabled": false, "reachable": false }, "mqtt_relay": { "enabled": false, "connected": false, "broker": "", "port": 0, "topic_prefix": "bambuddy" }, "homeassistant": { "enabled": true } }, "database_health": { "backend": "sqlite", "journal_mode": "wal", "quick_check": "ok", "db_size_bytes": 2490368, "wal_size_bytes": 4169472 }, "dependencies": { "fastapi": "0.135.3", "uvicorn": "0.44.0", "pydantic": "2.13.0", "sqlalchemy": "2.0.49", "paho-mqtt": "2.1.0", "psutil": "7.2.2", "httpx": "0.28.1", "aiofiles": "25.1.0", "cryptography": "46.0.7", "opencv-python-headless": "4.13.0.92", "numpy": "2.4.4" }, "log_file": { "size_bytes": 122018, "size_formatted": "119.2 KB" }, "network": { "interface_count": 2, "interfaces": [ { "name": "enp2s0", "subnet": "x.x.1.0/24" }, { "name": "macvlan-shim", "subnet": "x.x.1.0/24" } ] }, "websockets": { "active_connections": 1 } } ``` </details> **Logs (sanitized):** [bambuddy.log](https://raw.githubusercontent.com/maziggy/bambuddy/bug-report-assets/logs/3c5143b2d66b4b6db459bfe21401652b.log) --- *Submitted via BamBuddy Bug Report*

BreizhHardware

2026-05-06 12:31:51 +02:00

closed this issue
added the
user-report

bug
labels

BreizhHardware commented

2026-05-06 12:31:52 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 14, 2026):

The log you attached isn't useful for diagnosing this — debug logging was only enabled at 07:18:54, well after the print finished, so none of the FTP download / metadata extraction activity was captured.

Could you:

Enable debug logging before starting a new print (Settings → Support → Enable debug logging), then run a print that reproduces the bug and attach the fresh log.
Share one of the affected 3mf files — either drop the file directly, or tell me its approximate size (MB) and whether it's a multi-plate / multi-color project. "Large files" is relative; I'd like to know the threshold you're hitting.
Confirm the behavior on the affected row:
- Is there a thumbnail placeholder (broken image) or completely blank?
- If you open the archive detail page, is filament/cost empty there too, or just missing on the list?
- Does it eventually populate after a refresh or a few minutes, or stays empty forever?
Is this reproducible on every large print, or intermittent? A small print on the same printer populates correctly, right?

One thing I noticed in your sysinfo: you're on VP proxy mode with the A1. That means Bambuddy pulls the 3mf over FTP from the real printer after finish. With ftp_retry=10 and ftp_delay=30s, a failing download would block for ~5 min before giving up — the next debug log should make it obvious whether we're hitting an FTP timeout or a parser error.

@maziggy commented on GitHub (Apr 14, 2026): The log you attached isn't useful for diagnosing this — debug logging was only enabled at 07:18:54, well after the print finished, so none of the FTP download / metadata extraction activity was captured. Could you: 1. Enable debug logging before starting a new print (Settings → Support → Enable debug logging), then run a print that reproduces the bug and attach the fresh log. 2. Share one of the affected 3mf files — either drop the file directly, or tell me its approximate size (MB) and whether it's a multi-plate / multi-color project. "Large files" is relative; I'd like to know the threshold you're hitting. 3. Confirm the behavior on the affected row: - Is there a thumbnail placeholder (broken image) or completely blank? - If you open the archive detail page, is filament/cost empty there too, or just missing on the list? - Does it eventually populate after a refresh or a few minutes, or stays empty forever? 4. Is this reproducible on every large print, or intermittent? A small print on the same printer populates correctly, right? One thing I noticed in your sysinfo: you're on VP proxy mode with the A1. That means Bambuddy pulls the 3mf over FTP from the real printer after finish. With ftp_retry=10 and ftp_delay=30s, a failing download would block for ~5 min before giving up — the next debug log should make it obvious whether we're hitting an FTP timeout or a parser error.

BreizhHardware commented

2026-05-06 12:31:52 +02:00

Author

Owner

@PurseChicken commented on GitHub (Apr 14, 2026):

Commenting that I also have this issue when printing to a P1S. Following...

@PurseChicken commented on GitHub (Apr 14, 2026): Commenting that I also have this issue when printing to a P1S. Following...

BreizhHardware commented

2026-05-06 12:31:52 +02:00

Author

Owner

@PurseChicken commented on GitHub (Apr 14, 2026):

Not to totally hijack, but I noticed something in my logs (attached) from another issue I was looking at that seems relevant here too.

The log shows Bambuddy walking every known 3MF path on the printer's FTP and getting 550 on every one, then 425 once the data channel gave out:

12:13:57 FTP download failed for /data/Flexi_heart_..._plate_5.gcode.3mf: 550
12:14:00 attempt 4/4 returned failure
12:14:00 ERROR Download 3MF from /data/Flexi_heart_..._plate_5.gcode.3mf failed after 4 attempts
... repeats for /data/Metadata/, /, /cache/, /model/, /data/, /data/Metadata/ ...
12:16:03 FTP download failed for /Flexi_heart_..._plate_5.3mf: 425
12:17:06 attempt 3/4 returned failure
12:17:09 ERROR Download 3MF ... failed after 4 attempts
12:17:09 Direct FTP download failed, searching directories for 'flexi_heart_..._plate_5'
12:17:10 FTP list_files failed for /cache: 425
12:17:11 FTP list_files failed for /model: 425
12:17:12 FTP list_files failed for /data: 550
12:17:13 FTP list_files failed for /data/Metadata: 550
12:17:15 FTP list_files failed for /: 425

So every download path failed, every directory listing fallback failed, and then immediately after:

12:17:20 ERROR SECURITY: Refusing to delete files for archive 14 - file_path is empty or invalid: ''

Two things I'd flag as potentially relevant root causes on the FTP side:

The mix of 550 and 425 suggests the printer's FTP server was in a bad state by the time Bambuddy came looking — 550 on every candidate path implies the file was gone/moved, and 425 on the recursive listings implies the data channel couldn't be opened at all. Might be timing-related (printer cleans up the staged 3MF before Bambuddy finishes pulling it).
Bambuddy does have FTP retry configured (defaults: 3 attempts, 2s delay, 30s timeout), and the log shows it honoring that — 4 total attempts per path. The issue isn't the absence of retry, it's that the retry window is too tight for this failure mode: by the time Bambuddy starts pulling, the 3MF is already gone from every path on the printer (550s everywhere), and no amount of same-second retrying will bring it back. A longer delay between attempts, or a deferred retry minutes later, might catch it — but more importantly the archive row shouldn't be persisted with an empty file_path when every retry exhausts.

bambuddy-support-20260414-123112.zip

@PurseChicken commented on GitHub (Apr 14, 2026): Not to totally hijack, but I noticed something in my logs (attached) from another issue I was looking at that seems relevant here too. The log shows Bambuddy walking every known 3MF path on the printer's FTP and getting 550 on every one, then 425 once the data channel gave out: ``` 12:13:57 FTP download failed for /data/Flexi_heart_..._plate_5.gcode.3mf: 550 12:14:00 attempt 4/4 returned failure 12:14:00 ERROR Download 3MF from /data/Flexi_heart_..._plate_5.gcode.3mf failed after 4 attempts ... repeats for /data/Metadata/, /, /cache/, /model/, /data/, /data/Metadata/ ... 12:16:03 FTP download failed for /Flexi_heart_..._plate_5.3mf: 425 12:17:06 attempt 3/4 returned failure 12:17:09 ERROR Download 3MF ... failed after 4 attempts 12:17:09 Direct FTP download failed, searching directories for 'flexi_heart_..._plate_5' 12:17:10 FTP list_files failed for /cache: 425 12:17:11 FTP list_files failed for /model: 425 12:17:12 FTP list_files failed for /data: 550 12:17:13 FTP list_files failed for /data/Metadata: 550 12:17:15 FTP list_files failed for /: 425 ``` So every download path failed, every directory listing fallback failed, and then immediately after: ``` 12:17:20 ERROR SECURITY: Refusing to delete files for archive 14 - file_path is empty or invalid: '' ``` Two things I'd flag as potentially relevant root causes on the FTP side: - The mix of 550 and 425 suggests the printer's FTP server was in a bad state by the time Bambuddy came looking — 550 on every candidate path implies the file was gone/moved, and 425 on the recursive listings implies the data channel couldn't be opened at all. Might be timing-related (printer cleans up the staged 3MF before Bambuddy finishes pulling it). - Bambuddy does have FTP retry configured (defaults: 3 attempts, 2s delay, 30s timeout), and the log shows it honoring that — 4 total attempts per path. The issue isn't the absence of retry, it's that the retry window is too tight for this failure mode: by the time Bambuddy starts pulling, the 3MF is already gone from every path on the printer (550s everywhere), and no amount of same-second retrying will bring it back. A longer delay between attempts, or a deferred retry minutes later, might catch it — but more importantly the archive row shouldn't be persisted with an empty file_path when every retry exhausts. [bambuddy-support-20260414-123112.zip](https://github.com/user-attachments/files/26726761/bambuddy-support-20260414-123112.zip)

BreizhHardware commented

2026-05-06 12:31:52 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 15, 2026):

Please use dev branch and try again. If it still doesn't work, I need a new support package.

BTW: you support-bundle doesn't contain bdebug logs. You forgot to enable debug logging before generating the support package. https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

@maziggy commented on GitHub (Apr 15, 2026): Please use dev branch and try again. If it still doesn't work, I need a new support package. BTW: you support-bundle doesn't contain bdebug logs. You forgot to enable debug logging before generating the support package. https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging

BreizhHardware commented

2026-05-06 12:31:52 +02:00

Author

Owner

@mstko commented on GitHub (Apr 15, 2026):

I have printed two plates of the same 3mf file, almost same 6 hours print time. One of them appears ok in Archive, the other one not appear as i said in the first report. No photo, filament usage, image, etc. The only difference i saw in the slicer is that the one that doesnt load and even, dont take the finish photo in Telegram, its a complex stl with more than one million triangles... I dont know if this can cause the error but all files with this problem, have this in common.
I attach the two logs from the start till the end of both prints. If you need the 3mf file, tell me. Hope it helps

bambuddy-support-20260414-171430.zip

bambuddy-support-20260415-025010.zip

@mstko commented on GitHub (Apr 15, 2026): I have printed two plates of the same 3mf file, almost same 6 hours print time. One of them appears ok in Archive, the other one not appear as i said in the first report. No photo, filament usage, image, etc. The only difference i saw in the slicer is that the one that doesnt load and even, dont take the finish photo in Telegram, its a complex stl with more than one million triangles... I dont know if this can cause the error but all files with this problem, have this in common. I attach the two logs from the start till the end of both prints. If you need the 3mf file, tell me. Hope it helps [bambuddy-support-20260414-171430.zip](https://github.com/user-attachments/files/26744784/bambuddy-support-20260414-171430.zip) [bambuddy-support-20260415-025010.zip](https://github.com/user-attachments/files/26744789/bambuddy-support-20260415-025010.zip)

BreizhHardware commented

2026-05-06 12:31:52 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 15, 2026):

Thanks, this was very helpful. The 02:50 bundle's log window missed the print entirely, but the 17:14 bundle is the failing case — and the key line is Archive 226 has no file_path. That means the archive row was created at print start without a path to a 3mf, so on completion there's no file to extract filament/thumbnail/cost from, and the code correctly skips everything → empty row.

To narrow down why file_path wasn't set, could you:

Enable debug logging before the print starts, run a failing large-3mf print, and attach the log. I specifically need to see what's logged around the gcode_state IDLE → PREPARE → RUNNING transition.
Clarify whether the failing prints are started via BambuStudio/OrcaSlicer through the VP proxy, via SD-card print, or as a reprint from history. Mixing those changes how Bambuddy captures the 3mf.
If possible, attach the 3mf (or just its size and plate count) for one of the failing prints — the >1M triangle observation is a useful clue.

@maziggy commented on GitHub (Apr 15, 2026): Thanks, this was very helpful. The 02:50 bundle's log window missed the print entirely, but the 17:14 bundle is the failing case — and the key line is Archive 226 has no file_path. That means the archive row was created at print start without a path to a 3mf, so on completion there's no file to extract filament/thumbnail/cost from, and the code correctly skips everything → empty row. To narrow down why file_path wasn't set, could you: 1. Enable debug logging before the print starts, run a failing large-3mf print, and attach the log. I specifically need to see what's logged around the gcode_state IDLE → PREPARE → RUNNING transition. 2. Clarify whether the failing prints are started via BambuStudio/OrcaSlicer through the VP proxy, via SD-card print, or as a reprint from history. Mixing those changes how Bambuddy captures the 3mf. 3. If possible, attach the 3mf (or just its size and plate count) for one of the failing prints — the >1M triangle observation is a useful clue.

BreizhHardware commented

2026-05-06 12:31:52 +02:00

Author

Owner

@mstko commented on GitHub (Apr 16, 2026):

Hi, i have done a very large print to test this and get a full log. This is the Makerworld link https://makerworld.com/es/models/2539980-broly-legendary-super-saiyan-dbsuper?from=search#profileId-2796295 and i have printed the plate number 4. The exported gcode file is 37.5MB. I always send the prints from BambyStudio or Orcalicer, its depends. In this case, directly from BambuStudio.

Well, now the explanation. I sent the print and after a few hours, i saw that an entry was created in Archives. This entry had no thumbnail or any data except time. I take a log in that moment and the print continues. Before the print was finished, another entry was created, this time with all data but innacurate time. After finish print, no data was updated but the finish photo was taken. I take another log then.

Hope this helps.

bambuddy-support-20260416-052940.zip
bambuddy-support-20260415-202609.zip

@mstko commented on GitHub (Apr 16, 2026): Hi, i have done a very large print to test this and get a full log. This is the Makerworld link https://makerworld.com/es/models/2539980-broly-legendary-super-saiyan-dbsuper?from=search#profileId-2796295 and i have printed the plate number 4. The exported gcode file is 37.5MB. I always send the prints from BambyStudio or Orcalicer, its depends. In this case, directly from BambuStudio. Well, now the explanation. I sent the print and after a few hours, i saw that an entry was created in Archives. This entry had no thumbnail or any data except time. I take a log in that moment and the print continues. Before the print was finished, another entry was created, this time with all data but innacurate time. After finish print, no data was updated but the finish photo was taken. I take another log then. Hope this helps. <img width="806" height="542" alt="Image" src="https://github.com/user-attachments/assets/f697bd28-c0df-4420-8296-27f24223af97" /> [bambuddy-support-20260416-052940.zip](https://github.com/user-attachments/files/26772355/bambuddy-support-20260416-052940.zip) [bambuddy-support-20260415-202609.zip](https://github.com/user-attachments/files/26772354/bambuddy-support-20260415-202609.zip)

BreizhHardware commented

2026-05-06 12:31:52 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 16, 2026):

One error cause is, that you've restarted the container during an active print. Let me improve that a little bit.

@maziggy commented on GitHub (Apr 16, 2026): One error cause is, that you've restarted the container during an active print. Let me improve that a little bit.

BreizhHardware commented

2026-05-06 12:31:52 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 16, 2026):

Available/Fixed in branch dev and available with the next release or daily build. Please let me know if ti works for you now.

@maziggy commented on GitHub (Apr 16, 2026): Available/Fixed in branch dev and available with the next release or daily build. Please let me know if ti works for you now.

BreizhHardware commented

2026-05-06 12:31:52 +02:00

Author

Owner

@mstko commented on GitHub (Apr 16, 2026):

The error cause is, that you've restarted the container during an active print. Let me improve that a little bit.

Well, thats my fault... I have a Watchtower instance running to update the container...
The thing its that the first entry was created before the restart of the container i think... And it was generated again after the restart... Its that correct? I will try the next release and i will comment if its solved!

Thanks!! Bambuddy its amazing!

@mstko commented on GitHub (Apr 16, 2026): > The error cause is, that you've restarted the container during an active print. Let me improve that a little bit. Well, thats my fault... I have a Watchtower instance running to update the container... The thing its that the first entry was created before the restart of the container i think... And it was generated again after the restart... Its that correct? I will try the next release and i will comment if its solved! Thanks!! Bambuddy its amazing!

BreizhHardware commented

2026-05-06 12:31:52 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 16, 2026):

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

@maziggy commented on GitHub (Apr 16, 2026): ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!

BreizhHardware referenced this issue

2026-05-06 12:35:00 +02:00

[PR #686] [MERGED] [Fix]: Properly track filament usage data in Spoolman #1093

Rows
Columns

[GH-ISSUE #972] [Bug Report] It still doesn't load large files correctly in the Files tab. After the print fi #677

Screenshot