Snapshots and Undo Checkpoints

Before you run an optimization pass, a finite reschedule, or any bulk change you might want to walk back, capture a snapshot: a named checkpoint of the current schedule state, stored separately from your live production data.

Create Snapshot

Capture the current schedule as a named snapshot. Nothing about your live schedule changes when you do — a snapshot is a copy, not a mode switch.

Restore

Roll the schedule back to any saved snapshot in one click. This is the safety net for “that didn’t go the way I expected” — take a snapshot before a large optimizer run or a finite Accept, and if the result isn’t what you wanted, restore it.

Snapshots vs. Undo

These solve two different problems, and it’s worth knowing which one you actually want:

  • Undo/Redo (Ctrl+Z / Ctrl+Y) steps backward and forward through your own in-session staged edits — drags, mostly — before you Save. It’s short-range, client-side, and gone once you close the tab or Save. See Drag-and-Drop Rescheduling for how staging and Save actually work.
  • Snapshots are a deliberate, named checkpoint of the whole schedule that survives across sessions and across a Save — the tool for “before I run this optimizer pass / this finite reschedule, let me be able to get back to exactly where I am now,” not just “undo my last click.”

A reasonable habit: snapshot before anything you’d call a “run” (a finite Generate, an optimizer pass, a batch of manual changes you’re not fully sure about), and rely on Undo for the small stuff in between.

What a snapshot is not

A snapshot is a single stored state you can return to — it is not a side-by-side comparison of two competing plans, and SmartFlow doesn’t currently let you evaluate a what-if change (an extra shift, an expedited order) against a live baseline before committing to it. If you’re picturing scenario comparison, that’s a different, larger capability — see below.

Concepts behind this feature

For the fuller idea of what a genuine what-if comparison and a capable-to-promise ship-date quote actually require — solving two plans at the same instant, and why a quote is a projection rather than a reservation — see What-If Scheduling and Capable-to-Promise (CTP). For the narrower, related idea of protecting a plan you’ve already committed to, see Plan Stability: Frozen Horizons, Nervousness, and When to Reschedule.

This page explains what-if scenarios and capable-to-promise as a scheduling concept. What-if scenarios and capable-to-promise is on the SmartFlow APS roadmap and is not enabled in the current production release. For what SmartFlow APS does today, see the User Guide.

Ready to see finite scheduling on your own data?

Support: support@dynamicspro.ca · 416-843-6575

Get SmartFlow APS on AppSource