Viz Flowics does not have an automatic version history or rollback system. The only way to undo changes in the Graphics Editor is the Undo function, which works within the current browser session only.
How Undo works
Use Ctrl+Z (Windows) or Cmd+Z (Mac) to step back through recent changes one at a time. You can also go to Edit → Undo in the top menu bar.
Undo history is stored in your current browser session. It is permanently lost if you:
Reload or refresh the page.
Close the browser tab or window.
Navigate away from the Graphics Editor and come back.
Open the same package in a different browser or device.
If any of these happened before you tried to undo, the changes cannot be recovered.
I deleted something and refreshed the page — can I recover it?
No. Once you leave the editor session, the undo history is gone and the deleted content cannot be automatically restored. Flowics does not store editor session history on the server.
What you can do:
Rebuild the deleted element manually.
Check if a colleague has the same package open in the Editor without having refreshed — they may still have Undo history available.
Contact support with your package URL — the team can review account history and advise, but restoration is not guaranteed.
I want to go back to how the package looked yesterday or an hour ago
There is no time-based restore function. If the package was published after the change, that version is now the active one and cannot be automatically reverted.
Going forward: before any significant editing session, duplicate the package as a backup — click the three-dot menu on the package and select Duplicate. Name it clearly (e.g. "Package Name — Backup 2026-04-30"). If something goes wrong, re-publish the backup.
I made changes but did not publish — are they still there?
Viz Flowics auto-saves editor changes as you work, even if you do not click Publish. If you closed the browser without publishing:
Reopen the package in the Editor — your unpublished changes may still be there.
If another user opened and saved the same package in the meantime, their version will overwrite yours.
The Output always reflects the last published version, not the auto-saved draft. Auto-save protects your work in the Editor — it does not update what is on-air.
I accidentally sent the wrong content to a live graphic
Open the Remote Control immediately and enter the correct values in the Overlay Controls. Click Update Output to push the correction.
If the wrong content came from a Data Provider, correct it in the source (Google Sheets, JSON, etc.) and click Synchronize Connector.
If the wrong content was part of a template edit, press Ctrl+Z immediately if you are still in the same Editor session, then re-publish.
Best practices to prevent accidental data loss
Duplicate before editing live packages. Always work on a copy when making structural changes to a package that is in production.
Name backup duplicates clearly. Use dates or version numbers: "Lower Thirds — Backup 2026-04-30."
Use the Editor for testing. Changes in the Editor do not affect the Output until you publish — use this to preview and validate before going live.
Restrict editor access during live broadcasts. If multiple team members have access to the same packages, coordinate who can edit during a show to prevent accidental overwrites.
When to contact support
Contact the support team if you need help assessing what changes were made to a package and when. The team can review account activity, but cannot guarantee restoration of deleted content.
When contacting support, include: your Graphics Package URL and a description of what was changed and when.