Articles on: Cloud Slicer

Slice failed: what the error means and what to send support

Slice failed: what the error means and what to send support

When a slice fails, the Cloud Slicer shows the error it received or a clearer version of a known slicer-engine error. This article explains how to read the message and what to send if you need help.


What a failed slice means

A failed slice means the slicer did not produce a usable output file for the current model, printer, profiles, and settings.


The cause can be:


  • A model geometry issue
  • A profile issue
  • A printer or bed setup mismatch
  • Models too close together
  • A generated path outside the printable area
  • A slicer engine crash
  • A connection or result-download problem


Read the visible error first

The Cloud Slicer processes some known slicer errors and replaces them with clearer messages.


For example, it can recognize errors related to:


  • G-code path conflicts
  • Print-by-object conflicts
  • Invalid print or machine profiles
  • Generated paths outside the printable area
  • Floating regions or empty layers
  • Slicer engine crashes
  • A known relative-extruder profile issue


If the error has a Learn more link, open it before contacting support.


Try the safest fixes

Before contacting support, try the fixes that match the error:


  • Move models farther apart
  • Move the wipe tower away from models
  • Turn on supports for unsupported overhangs
  • Move models away from the bed edge
  • Switch print profile
  • Switch filament profile
  • Check machine profile and nozzle size
  • Try another slicer engine version
  • Re-export the model as STL or 3MF
  • Slice a simpler test model with the same setup


What to send support

If you still need help, send:


  • The Task ID shown in the slicer, if one is shown
  • The full error message shown in the slicer
  • The slicer engine and version
  • The printer or printer model selected
  • The machine profile, nozzle size, and bed type
  • The print profile and filament profile
  • Whether the same model slices in the desktop slicer
  • What you changed right before the failure started


Where to find the Task ID

Most failed slice tasks show a Task ID in the error area. Use the copy button next to it, then paste it into your message to support.


The Task ID helps support look up the failed slice attempt.


Some known errors show a guided Learn more flow instead of the Task ID block. In that case, open Learn more first and send support the visible error message, slicer engine, engine version, selected profiles, and what changed before the failure started.


Paying accounts and free accounts

If your account has support access, the slicer can open live chat with a prefilled message that includes the Task ID, raw error message, engine, and engine version.


If you do not have live chat access, use the community support option shown in the slicer and include the same information manually.


About replay files

For some failed slice tasks, SimplyPrint tries to upload a project replay in the background so support can investigate. This is automatic and not something you need to attach manually unless support asks for a file.


Still include the Task ID when one is shown, plus the visible error message. They are the most important pieces of information.



Updated on: 26/05/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!