This article answers common questions about pausing a Slice-connected store, order failures caused by using a tablet or another system alongside the Stream integration, and menu sync issues that are specific to Slice.
Why doesn't pausing my store on Slice seem to work?
Slice does not allow a pause of longer than 60 minutes. If you select a pause duration longer than 60 minutes, Slice rejects the request — your store will not show as paused, and no error message will appear.
To pause a Slice-connected store, choose a duration of 60 minutes or less.
Why did my Slice order fail with "Unknown order failure" or "order is already in terminal state"?
You may see the failure reason "Unknown order failure.", with additional details that include "(409) … conflict_error … order is already in terminal state".
This happens when an order is accepted, denied, or otherwise managed on the Slice tablet (or another integration) instead of through Stream. Once a store is connected to Stream, Slice expects order status changes to come from the integration only.
If the tablet or another tool processes the order first, Slice moves it to a final (terminal) state. When Stream's integration then tries to confirm that same order, Slice rejects the request with a conflict error, and the order shows as failed on Stream's side.
How to prevent it
Stop using the Slice tablet to accept, deny, or otherwise manage orders once the store is integrated with Stream — order status is now the integration's job.
Make sure all staff at the location know this, especially when a store first moves from tablet-only to integrated.
Why is my Slice menu failing to sync or publish?
One known cause is having two modifiers with the same name inside the same modifier group. Make sure every modifier within a group has a unique name before publishing your menu to Slice.
Please note we'll continue to add to this list as more causes are identified.