Signals Notebook: Avoid "Unsaved changes detected" when editing Text element

Problem

You may see a pop-up window with the message "Unsaved changes detected" while you are editing in a Text element.

Solution

Check the network condition

If the network doesn't have enough capacity to transfer the data in the Text element to the Signals cloud, the request for data synchronization may result in a timeout error, which causes the "Unsaved changes detected" message. Please make sure your network has a stable internet connection and enough capacity to upload/download standard documents.

Reduce the content size in the Text element

Signals Notebook allows you to add log text and multiple images in a Text element. However, including large content in a single Text element will be more prone to the "Unsaved changes detected" error. Especially if you have multiple images in the Text element, it is recommended to reduce the number of images or their size.

When you make an update to the content of the Text element, your browser sends the entire data of the Text element to the Signals cloud. Reducing the size of the content will ensure that data transfer is more stable.

Wait until the change is "saved"

To reduce the risk of losing the change you add to the Text element, it is recommended to wait until you see the "Saved" message at the bottom-right corner of the Text element.

While this status message is "Saving", the data in the Text element is being synchronized. It is good practice to wait until the status changes to "Saved" before proceeding to the next edit. 

When  you see "Unsaved changes detected" while editing a Text element:

You can wait for approximately one minute to see if the pop-up window is dismissed automatically. The Text element is retrying synchronization, and if it succeeds, the pop-up will disappear.

You can also refresh the page in your browser to load the content from the Signals cloud. In this case, the unsaved changes will be lost in the Text element because they are not saved in the cloud.