Creating a Sandbox

Creating a Sandbox

Forking a Production Run

1

Open any production run in PENDING or IN PROGRESS status

Closed runs can also be sandboxed for analysis, but cannot be promoted back to production.
2

Click Create Sandbox

The platform creates a deep copy of the run: patterns, order allocations, and machine snapshot are all duplicated.
3

Name the sandbox

Give it a descriptive name so you can identify it among multiple sandboxes of the same run.

What Gets Copied

  • All patterns with their width slots and repetition counts
  • Order allocations (which order goes to which pattern)
  • Machine configuration snapshot at time of original run creation
  • Run metadata (customer references, scheduled date)

What does not get copied: waste events logged against the live run (sandboxes start with zero waste events), and closed/dispatched status.

Naming & Organisation

Each run can have up to 10 active sandboxes simultaneously. Sandboxes are listed in the run detail view under a collapsible Sandboxes panel. You can archive sandboxes you no longer need without deleting them. They remain visible in the archive for audit purposes.

Previous

Introduction

Next

Modifying & Comparing

Was this page helpful?

Something unclear or missing? Reach out and we'll update this page.

Give Feedback