Currently, there are cases where changes made in the FlowEditor are not saved, leading to potential data loss for the user. This issue has been noted in issue glific/floweditor#155.

To address this, we will implement a mechanism to store flow changes locally using localStorage. This ensures that even if a save or publish action fails, the user’s latest changes are not lost.

Solution:

• Store changes in localStorage on every edit or interval while using the FlowEditor.
• On publish, prioritize the most recent changes from localStorage if there is a discrepancy with the saved version.