The symptom pattern
The reports follow a common script: a print ends abnormally — cancelled from the Bambu Handy app mid-job, interrupted by a network dropout, or following a failed print — and afterwards the app and/or the printer’s display continue to show the old job as “printing” at a frozen percentage. Attempting to start a new job from the slicer returns an error that the printer is busy, while the toolhead sits parked and cold. Nothing is actually running.
What’s actually happening
This is a state-synchronisation problem, not a hardware fault — worth saying loudly, because the symptom description (“printer stuck, won’t respond”) sends people hunting for hardware problems that don’t exist. The printer’s job-state record isn’t cleared when a job ends abnormally, and while it persists, the cloud service keeps reflecting the stale state back to every connected client. That’s why the phantom job can appear simultaneously on the printer’s display, in Bambu Handy, and in the slicer’s device view.
Recurrence appears to depend on firmware version and on whether the printer is in cloud or LAN-only mode, which is why the firmware release notes are worth checking if it keeps happening.
Clearing it
In order of preference, per user reports and Bambu Lab’s own troubleshooting guidance:
- Clear or finish the job from the printer’s front display, if it offers the option.
- Do a full power cycle from the physical switch — off, wait ten seconds, on. This is the reliably reported fix.
- If the app still shows the phantom job after the printer restarts, force-quit and reopen the app so it re-syncs against the printer’s now-clean state.
Verdict
A nuisance-level fault with a zero-cost fix. Keep the firmware current — release notes have periodically mentioned job-state and sync fixes — and consider LAN-only mode if it recurs frequently on your network. No repair, no parts, no teardown.