Articles on: Printing: start, queue & track

How to read the print job timeline

How to read the print job timeline


Open any job from your print history and you will see a timeline at the bottom of the page. It is a chronological record of everything that happened to the print, from when the file was created through to a clean bed. While a print is running, the timeline updates live, so you can watch events appear in real time.


This guide explains every kind of event you might see and what it means.


Contents


Where to find the timeline

Go to Print history in the left menu (or simplyprint.io/panel/jobs), then click any job to open its detail page. The timeline runs down the page below the job header, info box, and material box.


Job detail page with a full timeline of events


Each entry has an icon, a title, a timestamp, and often a short note or a snapshot image captured at that moment. Events run in chronological order, with the job's creation at the top and the most recent event at the bottom.


Live updates during a print

If the job is still printing, the timeline streams events as they happen. SimplyPrint subscribes to the printer's live state, so a pause, a resume, an AI detection, or the final result shows up without you reloading the page. When the print finishes, the closing event (done, stopped, or failed) is added automatically.


The core events

Every job has at least these:


  • Job created - when the file was queued or the print was set up.
  • Print started - when the printer actually began printing. A snapshot from the camera is attached if one was taken.


From there, the timeline fills in whatever happened during the print.


Timeline showing the created and started events


Pauses and resumes

A pause shows up as its own event, and so does the resume that follows it. SimplyPrint labels the pause by what caused it:


  • Manual pause - a person paused the print. If your account tracks it, the timeline shows who.
  • Print paused by AI - AI failure detection paused the print based on your AI settings.
  • Filament runout pause - the printer's filament sensor triggered the pause.


When the print continues, a resume event is added.


A paused event followed by a resume event


Filament changes

If filament was swapped mid-print, a filament change event records it, with the new spool's brand, colour, and type. On a multi-extruder printer it also notes which extruder, and how far into the print the change happened.


AI events

When AI failure detection is watching a print, its activity is woven into the timeline. You may see:


  • AI detected failure - the AI flagged a likely failure such as spaghetti, warping, or a blob.
  • AI paused print - the AI paused the print as a configured action.
  • AI cancelled print - the AI cancelled the print as a configured action.
  • AI walked back prior detection - the AI revised an earlier detection (a false positive it later corrected).


Each AI event shows a confidence score (0 to 100%) and, where available, the snapshot the AI was looking at. For an AI-caused pause, failure, or cancel, a Why? button expands the triggering inference, with the action it took, the confidence, and how many things it detected.


An AI failure detection event with score and snapshot


Bed checks

When AI bed-check runs (it runs under AutoPrint to confirm the bed is clear before the next job), the timeline records the result:


  • AI confirmed the bed is clear
  • AI detected bed not clear


If the bed was checked several times in quick succession, those attempts are collapsed into one expandable group showing the final result. Click the Show all attempts button to see each individual check, its image, and its status.


How a print ends

The closing event reflects the outcome:


  • Print done - the print finished successfully, with a final snapshot.
  • Print stopped - the print was cancelled. The timeline shows the cancel reason and any comment. On an organization account it can also show who cancelled it (and flags it if that was not the person who started it). If the AI cancelled it, the event reads "Print cancelled by AI".
  • Print failed - the print failed. If a failure reason was recorded, it is shown.


Two more events can appear at the end:


  • Bed cleared - the bed was cleared after the print, noting whether a person or the AI confirmed it.
  • Job archived - the job was archived, noting who archived it and any reason given. A job can be archived even before it ends.


You can also see skipped-object events, which record when a single object on the plate was skipped mid-print (the object name and the percentage at which it was skipped).


The closing 'done' event and a bed-cleared event


Rating AI detections

On any AI event you can give a thumbs-up or thumbs-down to tell us whether the detection was good or bad. This feedback trains the model and improves future detections. Once you rate an event, the buttons lock in. If you mark a detection as bad, a shortcut to your AI settings appears so you can adjust the printer's sensitivity.


Rating detections is the single most useful thing you can do to make the AI better for your prints. A few thumbs-down on false positives goes a long way.



Updated on: 26/06/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!