Skip to content

Commit 3bd9300

Browse files
Update git-snapshot-for-iiot-flows.md
1 parent 296e806 commit 3bd9300

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

src/blog/2026/05/git-snapshot-for-iiot-flows.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "See Exactly What Changed in Your IIoT MOC Review with Git-Style Diffs"
2+
title: "See Every Logic Change in Your IIoT MOC Review with Git-Style Diffs"
33
subtitle: "How FlowFuse snapshot comparison gives IIoT teams a verifiable, auditable review of every logic change before it reaches the machine"
44
description: "Most IIoT teams have a MOC process. What they lack is visibility into the actual logic change. FlowFuse snapshot comparison shows reviewers exactly what shifted between deployments, node by node, line by line, before anything is deployed."
55
date: 2026-05-21
@@ -55,4 +55,4 @@ When the reviewer has worked through the diff, they approve the named snapshot.
5555

5656
In FlowFuse, the reviewed artifact and the deployed artifact are the same thing. For audits, incident investigations, and regulatory compliance, that traceability is what MOC was always meant to produce.
5757

58-
For teams on Team or Enterprise plans, FlowFuse also creates auto snapshots on every deploy, a passive safety net that captures the exact state running on each instance or device, even when a named snapshot was not part of the workflow. Up to ten auto snapshots are retained automatically, giving teams a recoverable history without any extra steps. The same approved snapshot can also be pushed to an entire fleet without re-entry. The [full snapshot documentation](/docs/user/snapshots/) covers every available action.
58+
For teams on Team or Enterprise plans, FlowFuse also creates auto snapshots on every deploy, a passive safety net that captures the exact state running on each instance or device, even when a named snapshot was not part of the workflow. Up to ten auto snapshots are retained automatically, giving teams a recoverable history without any extra steps. The same approved snapshot can also be pushed to an entire fleet without re-entry. The [full snapshot documentation](/docs/user/snapshots/) covers every available action.

0 commit comments

Comments
 (0)