Articles on: Cloud Slicer

Cloud Slicer error messages and what they mean

Cloud Slicer error messages and what they mean


This guide lists the Cloud Slicer messages people ask about most, what each one means, and how to fix it. Find your message below, follow the steps, then check that slicing works again.


Some messages come from SimplyPrint. Others come straight from the slicer engine (Bambu Studio, OrcaSlicer, Creality Print and so on), and those usually name the exact setting that is wrong.


In this guide


Missing filament profile or "No filament profile selected"

The full message is Missing filament profile - No filament profile selected. Slicing is disabled.


A slicer filament profile is not the same as a material profile. Material profiles (Settings > Filament > Material profiles) describe your spools for inventory, cost and preheating. The slicer needs a slicer filament profile, which holds the temperatures, cooling and flow the engine slices with.


  1. In the Cloud Slicer sidebar, look at the filament cards and pick a filament profile under the filament that has none.
  2. If the profile you want isn't in the list, go to Settings > Slicing > Profiles.
  3. Choose the same slicer engine you slice with, set the profile type to Filament, and create or import the profile.
  4. Make sure the profile is made for your printer, then go back to the slicer and select it.


Check: the red message disappears and the Slice button is no longer blocked.


Why: a profile only shows up for the engine and printer it was made for, so a profile made for another engine or printer stays hidden.


Similar messages work the same way: Missing filament (no filament picked for a filament card an object uses) and Missing filament material (the filament has no material type).


Missing print profile, or no print profiles to choose from

The message is Missing print profile - No print profile selected. Slicing is disabled.


  1. Open the print profile selector in the sidebar and pick a profile.
  2. If the list is empty, check the printer, nozzle size and slicer engine at the top of the sidebar. Print profiles are made for one printer and nozzle size.
  3. If you slice for one of your own printers and the list looks wrong, select the printer model in the printer picker instead of the printer itself, then add the filaments you need with Add filament.


Check: a print profile is selected and the message is gone.


Why: the list puts the print profiles that match the filaments your plate prints with first. If none match all of them, you still see the whole list, so the selector is never empty because of the filaments loaded in your printer.


If no profile exists for your printer at all, see Why a printer, machine, filament, or print profile is missing.


The settings sidebar is missing

You can load a model, but there are no settings on the side: no printer, filament, nozzle or print settings.


  1. Look for the ☰ (Toggle sidebar) button at the left end of the top toolbar and click it. The settings open as a panel.
  2. If you'd rather have the sidebar always visible, reset your browser zoom to 100% (Ctrl + 0 on Windows and Linux, Cmd + 0 on Mac) or make the browser window wider.


Check: the printer, filament and print settings are visible.


Why: when the browser window is narrower than about 1,120 pixels, the slicer tucks the settings into a panel behind the ☰ button to make room for the 3D view. Zooming in has the same effect as a narrower window, so a laptop that switched to a higher zoom level can hide the sidebar overnight.


The temperature difference of the filaments used is too large

The full message from the Bambu Studio engine reads: The temperature difference of the filaments used is too large. Please verify the slicing of all plates in Bambu Studio before uploading.


The engine refuses to print a high-temperature and a low-temperature filament together, because it can clog the nozzle.


  1. In the object list, check the filament number next to each object and each part. Make sure every one uses the filament you mean to print with.
  2. In the sidebar, remove the filament cards you don't use for this print with the × on each card.
  3. Slice again.


Check: the slice finishes without the error.


Why: an object or part can still be assigned to another filament, for example after importing a 3MF that was set up for several colours. Removing a filament card only changes this slicing session. It doesn't change the filaments loaded in your printer, and they come back when you reload the slicer.


If you really are printing two filaments with very different temperatures, pick filaments that print at similar temperatures, or adjust the temperatures in their filament profiles.


Some versions of the message add "you can enable the option in Preferences". That option is in the Bambu Studio desktop app. The Cloud Slicer doesn't have it, so it can't print a high-temperature and a low-temperature filament together.


Too small line width

The full message from the Creality Print engine reads: Too small line width. There are some incorrect slicing parameters in the 3mf.


The message says what is wrong: a line width setting is lower than the printer can physically print.


  1. In the sidebar, type line width in Search for a setting. If nothing shows, switch the settings mode at the top of the settings to the most detailed one and search again.
  2. Raise the line width values that are very low or 0. Line widths are often set as a percentage of the nozzle size, for example 100%.
  3. Check that the nozzle size at the top of the sidebar matches the nozzle on your printer.
  4. Slice again.


Check: the slice finishes without the error.


Why: engine messages like this come straight from the slicer engine, not from SimplyPrint, and they usually name the setting to change. Searching the exact message online also helps, because other users of that engine have hit it before.


Could not verify your slicing quota

The message is Failed to load usage limits - Could not verify your slicing quota. Please retry to continue.


  1. Click Retry in the message.
  2. If it comes back, reload the page.


Check: the message disappears and the usage counter at the bottom of the slicer shows your slices again.


Why: the slicer checks your slice allowance with the slicing service when it opens. If that check doesn't get through, for example on a brief connection drop, the slicer can't confirm your allowance. Retrying fixes it in almost every case. It does not mean your allowance or trial has run out.


Max concurrent tasks exceeded

This message means a slice is already running for you, and the slicer won't start another one at the same time.


  1. Wait for the running slice to finish, then slice again.
  2. If you started a slice in another tab or on another device, finish or cancel it there.
  3. If no slice is running anywhere, wait a little and try again. A slice that got lost on the way is cleared automatically: after 30 minutes if it never started, or after about an hour if it started but never finished.


Check: the next slice starts.


Why: you can run one slice at a time from the panel. This is a limit on slices at the same time, not on how many you can do in a month. See Cloud Slicer quotas, limits, and usage.


Stuck on "Preparing file"

Preparing file is the first step of a slice: your browser packs the model and settings before they are uploaded. If it never moves on:


  1. Reload the page.
  2. Select your printer again in the printer picker, then slice.
  3. Still stuck? Try a private (incognito) window or another browser. See Stuck on loading? Clear cache, try incognito or another browser.


Check: the progress moves on to Uploading, In queue and Slicing.


Why: this step runs in your browser, so a stale page, a browser extension or a printer selection that no longer matches your account can stop it.


We couldn't start the slicer (WebGL)

The slicer shows We couldn't start the slicer, with a technical note about WebGL. The Cloud Slicer draws the 3D view with WebGL, a graphics feature in your browser.


  1. Click Open WebGL test in the message, or go to get.webgl.org, and check whether the page says your browser supports WebGL.
  2. If it doesn't, turn on WebGL in your browser. See How to enable WebGL in major browsers.
  3. Update your graphics drivers and restart the browser.
  4. Try another browser (Chrome, Edge, Firefox or Safari).


Check: the slicer opens with the 3D build plate.


If the WebGL test works but the slicer still won't start, open Technical details in the message, copy them with the copy button, and include them when you contact support.


Getting help with a failed slice

When a slice fails, the error box shows a Task ID. Support can use it to look up the failed slice.


  1. Click the copy icon next to Task ID.
  2. On a paid plan, click Contact support with your Task ID. A chat opens with the Task ID, the error message and the engine version already filled in. On the Free plan, click Join our Discord and paste the same details there.
  3. If support asks for your setup, right-click an empty spot on the build plate and click Export configuration. This downloads a .sps file with your models, plates and settings, which you can send along.


Check: your message to support includes the Task ID and the full error text.


When the slicer engine itself fails, the slicer sends a copy of your setup to SimplyPrint along with the Task ID, so the Task ID is often all support needs.


Export configuration isn't in the menu? Then your user group can't download files other people uploaded, and the file you opened is one of them. An account admin controls this with the Can download files uploaded by others permission. Send the Task ID and the full error text instead, or ask someone who can download the file to export the configuration. See Preventing file downloads.


Some known errors show a Learn more link instead of the Task ID. Open it first, because it explains that error. More on reading errors: Slice failed: what the error means and what to send support.


Updated on: 27/10/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!