Cloud Slicer limits & queue

Cloud Slicer limits and queue

Cloud Slicer usage is controlled by your account's monthly slice allowance. The slicer may also show a queue when slice jobs are waiting to run.

This is separate from the SimplyPrint print queue. The print queue controls when prints are sent to printers. The Cloud Slicer queue controls when slicing tasks are processed.

Monthly slice usage

Your account may have a monthly number of Cloud Slicer jobs. In the slicer, you may see a counter such as 12 / 15 left this month.

When the counter reaches zero, slicing is limited until your allowance resets or your plan changes.

Slicing queue

When you start slicing, the Cloud Slicer sends the task to SimplyPrint's slicing service. If there are other tasks ahead of yours, the slice waits in the slicing queue.

This does not mean the file has been added to your printer's print queue. It only means the slicing task is waiting to be processed.

"Max concurrent tasks exceeded"

This message means you already have a slice running and tried to start another at the same time. It is a limit on how many slices you can run at once, not a limit on how many you can do per month, and it has nothing to do with API request limits.

Most plans can run one slice at a time.
Print Farm and higher can run two at a time.

If you see it, wait for the running slice to finish and then start the next one. If a slice appears stuck, give it a little time - stuck tasks are cleared automatically after about 30 minutes - then try again. Slicing several plates from one file at once (multi-slice) is handled for you and does not hit this limit.

Print queue

After slicing is complete, you can choose what to do with the sliced output:

Download it.
Save it to SimplyPrint.
Add it to the print queue.
Start a direct print, when available for your setup.

For those actions, see How to download, queue, direct print, or multi-print sliced output.

Why slicing can be unavailable

Slicing may be unavailable when:

You have no monthly slice jobs left.
The selected printer, machine profile, filament profile, or print profile is not compatible.
A required profile is missing.
The selected engine cannot slice the current setup.
Your role does not have permission to use the needed slicer feature.

Why do i have a limited amount of slices?

While the many amazing slicers we carry are free to use for everyone, and completely open-source, running them is not. They are heavy, computationally expensive programs, with real costs to maintain and provide servers to host them. To ensure fair and even access for all our users, free users have a limited amount of monthly slices. We offer all available resources to any and all paying ecosystem and cloud slicer users, by guaranteeing enough capacity for unlimited use of all our capacity.

What is local slicing?

The counter-side of cloud-slicing is slicing locally on your device, there are both upsides and downsides to this. Typically on low-powered hardware it is not feasible to run the full desktop slicers, solutions to this is typically using specialty slicers like Kiri:Moto that is designed to run in the browser. But even then the speed of slicing depends on the device it is running on. On powerful hardware you might still want to use a cloud-based slicer to get the same profiles, role based access control on multiple levels and easy access to your printers for material awareness or sending prints directly.

Updated on: 27/07/2026

Was this article helpful?

Thank you!