Skip to content

Tips & Troubleshooting

Check the status under the diagram’s name in the ribbon. A diagram saved to the cloud autosaves, and reads Saved to cloud when it’s safe; reopen it from File → Open from Cloud. If it was changed in a way you didn’t want, File → Version history can take it back to an earlier state.

A diagram that was never saved to the cloud (the status reads Local or Not saved) exists only on your canvas until you save it — Schema warns before you close the tab with unsaved changes, but can’t recover them afterwards. See Saving & Opening.

“It says the diagram changed somewhere else”

Section titled ““It says the diagram changed somewhere else””

Someone — or another of your own tabs — saved the same cloud diagram after you opened it. Schema stops rather than overwrite their work, and asks whether to save yours as a copy, load theirs, or overwrite. See Saving & Opening.

“A device has a red badge and I haven’t written any rules”

Section titled ““A device has a red badge and I haven’t written any rules””

That’s a built-in network check: most often two devices with the same IP address, or an address that isn’t inside the subnet of the segment the device is drawn in. Hover the badge or open Health in the ribbon to see which.

“A compliance warning showed up and I don’t understand why”

Section titled ““A compliance warning showed up and I don’t understand why””

Hover the badge, or open the node’s Properties panel (right-click → Properties) — the exact rule message is shown there. If it’s not obvious why the rule fired, check:

  • Is the rule’s IF row scoped to Any node? That’s broader than it sounds — see Scope your rules carefully.
  • For a “must have in path” or “must NOT have in path” rule, remember it checks the node’s entire reachable connection graph, not just direct neighbors — a node several hops away still counts.

“A warning I expected to see isn’t showing”

Section titled ““A warning I expected to see isn’t showing””
  • Confirm the rule is Enabled in the Compliance Rules editor — a disabled rule is skipped entirely.
  • Double check the rule’s IF row actually matches the node’s icon type — a rule scoped to “Server” won’t evaluate against a “Database” node even if they seem similar.
  • If you’re checking a field (like IP Address), make sure you’re looking at the right view — Engineer and Manager views have completely separate rule sets and node data.

“Fit View zoomed in way further than I expected”

Section titled ““Fit View zoomed in way further than I expected””

Fit View zooms to fill the screen with whatever’s on the canvas — for a single node, or a couple of nodes close together, that can mean zooming in quite far, since there’s little content to “fit” against. Add more of your diagram, or zoom out manually with your mouse wheel or View → Zoom out, if the auto-fit result feels too tight.

“The editor says it needs a bigger screen”

Section titled ““The editor says it needs a bigger screen””

Building diagrams needs room for the ribbon, the icon palette and the canvas, so on a phone-sized screen Schema says so rather than showing something unusable. You can continue anyway (it’s workable on a tablet in landscape), and shared links open fine on any device.

  • Give segments their subnet. One field in a segment’s Properties turns on address checking for everything inside it.
  • Use zones and segments deliberately. They’re not just visual grouping — they drive automatic edge coloring and several compliance conditions. A diagram with real containers around real boundaries is far more useful than one with everything loose on the canvas.
  • Let orange edges guide a review. Since boundary-crossing connections render orange automatically, scanning for orange lines is a fast way to review a diagram for connections that deserve a second look.
  • Name rules as the message you want to see. A rule’s name is the warning text — write it that way from the start rather than a short internal label.
  • Keep Manager View honestly simple. It’s tempting to just duplicate the Engineer View wholesale — the real value comes from actually collapsing detail down to what a non-technical stakeholder needs to see.