Skip to main content

Anyone else frustrated with Gong Engage's lack of auto-saving of draft changes?

  • April 20, 2026
  • 2 replies
  • 24 views

Forum|alt.badge.img

Working through my third iteration of making changes an email flow template. During my first attempt, I clicked “save” and got the save confirmation—upon refresh the content of a multi-step draft of a flow was wiped. The second time, I navigated away and clicked the “leave anyway” option too quickly. 

 

The save button on the drafting window seems to work ok, but it sometimes takes clicking it many times to actually save the persist the unsaved changes. 

 

Is anyone else frustrated with the lack of autosaving on draft changes? I find this to be severely lacking and not up to date with current editing fields for long-form text boxes in an editor. Back to editing to try to reproduce the copy I had written initially. 

2 replies

Nisha Baxi
  • Community Manager
  • April 21, 2026

@Sean Reed This sounds super frustrating! I am sending this to our Engage team so they can look at it more closely as both a potential reliability issue and a product gap around autosaving long‑form edits

In the meantime, a couple of imperfect workarounds that may reduce the risk of losing work:

  • When you’re making bigger changes, give the “Save” button a moment and then refresh once to confirm the flow has truly updated before moving on.

  • For really long email copy, draft in an external editor first (Google Doc/Notepad/etc.), then paste into the flow once you’re happy with it — just until we can improve the in‑product experience.


Carly Lohnberg
Forum|alt.badge.img

@Sean Reed To follow Nisha’s recommendations, I have filed a feature request for auto save capabilities.   Some of your experience like having to click save multiple times and saving then refreshing to find your content gone sounds like an issue.  If you are able to recreate this or you run into it again, can you file a Support ticket?  That will allow us to look into the issue and hopefully resolve it.  Thanks!