Keep a Print Failure Log That Makes Troubleshooting Faster

Record the original job before changing it

A failure log preserves the state you need to compare later. Save the slicer project, not only the mesh, and label the exported print file. Record the printer model, installed nozzle, plate, material product, slicer version, and profile names. Note whether the failure began immediately, at a repeated height, after a long run, or following a hardware change. Those clues narrow the next test more than a list of every available setting.

Describe observations rather than conclusions

Write “extruder clicks after ten minutes and wall lines become thin” rather than “bad nozzle.” The first description remains useful if the cause turns out to be heat creep, spool resistance, or excessive flow demand. Photograph the whole part and the affected region under clear light. Include the underside for adhesion problems and mark the front of the bed so spatial patterns remain interpretable.

Define a single-variable trial

For each test, write a question, a change, and a pass condition. An example question is whether slower printing removes missing lines on a wall. Keep material, temperature, nozzle, and geometry fixed while changing the relevant speed or flow limit. If the part improves, the result supports a throughput-related cause but does not alone identify a clog or prove a universal maximum speed.

Preserve failed outcomes

A failed adjustment is useful evidence. Record whether the symptom was unchanged, reduced, or replaced by another defect. Restore the baseline before testing a different explanation. Without this step, a later improvement can depend on several forgotten changes. Include approximate print duration and material used so you can prefer a short diagnostic sample over repeated full-size failures.

Build a transferable record

For community or manufacturer support, provide the model-specific details, a short sequence of tests, and relevant photos. Remove private file names or personal details before sharing. Do not present a successful test on one printer as a guarantee for another. The valuable output is a reproducible path from an observed defect to a verified improvement, including any limits that remain.

A template you can copy

Use one entry per comparison. Leave unknown information blank rather than guessing. This template works in a text note, spreadsheet, or a support ticket.

Job ID / date:
Printer / firmware:
Nozzle product and diameter:
Filament product / color / condition:
Build plate and side:
Slicer version / profile names:
Saved project and exported file:
Observed symptom / time or height:
Photo labels and bed orientation:
Question being tested:
Baseline value -> changed value:
Conditions kept the same:
Pass condition:
Result: unchanged / improved / worse / different defect
Repeat result:
Restored baseline / next action:

Example: do slower moves restore missing lines?

Suppose a wall has complete lines at the beginning but gaps in a faster region. A useful question is whether lower extrusion demand improves that region. Use the same short sample and change only the relevant speed or flow limit within the supported profile. Record both values and check the same region after cooling.

If the gaps decrease, write that observation. Do not write “hotend fixed”: lower demand can help several conditions, including an unresolved restriction. If a repeat produces gaps again, keep both results. If filament was dried between attempts, add that fact; the experiment no longer isolates speed alone. This example describes a proposed investigation, not a result we obtained on a printer.

Make the record small enough to maintain

Keep an overall photo, one close-up, and the saved project for each meaningful attempt. Identify orientation consistently and avoid reusing file names such as “final” for multiple exports. Separate slicer estimates from measured material or time. Before sharing a project publicly, inspect custom G-code, filenames, account information, and model licensing.

For Bambu users, include the selected plate and nozzle profile, whether bed leveling ran, and any exact device error. Our Bambu first-layer checklist gives an example of the information needed for an adhesion investigation. A screenshot of a successful calibration message does not replace a description of the actual print.

Minimum evidence to preserve

Check	Evidence to keep
Job identity	Save the project and label printer, nozzle, material, and profile.
Observed failure	Record time or height, bed orientation, sound, and photos.
Hypothesis and trial	Write a single change with its previous value and a pass condition.
Outcome	Keep failed results, restored baselines, and repeat observations.

Scope

This is a general workflow for recording and checking FDM jobs, not a report of a physical product test. Follow the documentation for your exact printer and slicer when commands or service procedures differ.