Is there an existing issue for this problem?
CrealityPrint Version
7.2.5251
Operating System (OS)
Linux
OS Version
Ubuntu 24.04.4 LTS
Additional system information
Intel(R) Core(TM) i7-5500U CPU @ 2.40GH
ram: 8Gb
Intel Corporation HD Graphics 5500 (rev 09)
Printer
creality K2 SE
How to reproduce
Steps to reproduce
- In AI Edition, slice a model using the "Hyper PLA @creality K2 SE 0.4 nozzle" profile (or any profile where bed temp triggers the 1000C001 warning).
- Observe in the logs (or UI) that the slice result includes:
"warnings":[{"error_code":"1000C001","level":1,"message":"bed_temperature_too_high_than_filament"}]
- Observe a corresponding workflow update:
[SAgentMQTT][WorkflowUpdate] ... current_card_type=slice-confirm ... pending_tool=start_slice pending_request_id=...
- Send the job to the printer over Wi-Fi using the normal "send to printer" button.
- Printer screen shows "No tasks currently" / stays Idle, nozzle and bed targets remain at 0°C.
- The job never appears in the printer's local job queue/history, even though the app-side slice result reports success.
- Exporting the G-code and loading it via USB, or via the printer's local web UI, works immediately without issue.
Expected behavior
Either the temperature warning should be surfaced clearly enough that the user can dismiss/confirm it and proceed, or (if already acknowledged) it should not silently block the Wi-Fi send pipeline.
Actual results
Actual behavior
The slice-confirm card / pending start_slice request appears to get stuck in a pending state, and the print job silently never reaches the printer's queue over Wi-Fi, despite the app reporting a fully successful slice.
Expected results
Additional notes
This is consistent across multiple independent sessions (observed on 2026-07-18 and 2026-07-19), always with the same bed_temperature_too_high_than_filament warning and the same slice-confirm / pending_tool=start_slice pattern. This may be specific to the AI Edition workflow introduced in 7.2.0 — switching to Professional Edition may avoid triggering the confirmation-card flow. Happy to attach full debug logs (~/.config/Creality/Creality Print/7.0/log/debug_*.log.0) if maintainers want to see the complete workflow_id/session_id trace.
Project file & Debug log uploads
issue_creality_print.zip
Checklist of files to include
Anything else?
No response
Is there an existing issue for this problem?
CrealityPrint Version
7.2.5251
Operating System (OS)
Linux
OS Version
Ubuntu 24.04.4 LTS
Additional system information
Intel(R) Core(TM) i7-5500U CPU @ 2.40GH
ram: 8Gb
Intel Corporation HD Graphics 5500 (rev 09)
Printer
creality K2 SE
How to reproduce
Steps to reproduce
"warnings":[{"error_code":"1000C001","level":1,"message":"bed_temperature_too_high_than_filament"}]
[SAgentMQTT][WorkflowUpdate] ... current_card_type=slice-confirm ... pending_tool=start_slice pending_request_id=...
Expected behavior
Either the temperature warning should be surfaced clearly enough that the user can dismiss/confirm it and proceed, or (if already acknowledged) it should not silently block the Wi-Fi send pipeline.
Actual results
Actual behavior
The slice-confirm card / pending start_slice request appears to get stuck in a pending state, and the print job silently never reaches the printer's queue over Wi-Fi, despite the app reporting a fully successful slice.
Expected results
Additional notes
This is consistent across multiple independent sessions (observed on 2026-07-18 and 2026-07-19), always with the same bed_temperature_too_high_than_filament warning and the same slice-confirm / pending_tool=start_slice pattern. This may be specific to the AI Edition workflow introduced in 7.2.0 — switching to Professional Edition may avoid triggering the confirmation-card flow. Happy to attach full debug logs (~/.config/Creality/Creality Print/7.0/log/debug_*.log.0) if maintainers want to see the complete workflow_id/session_id trace.
Project file & Debug log uploads
issue_creality_print.zip
Checklist of files to include
Anything else?
No response