How do you preserve unsaved script edits in an AI portal?

How do you preserve unsaved script edits in an AI portal?

An editor needs to distinguish what the user has typed from what the server has accepted. Treating those states as identical can lose changes or generate media from outdated text.

Track dirty and saved state

Keep the current local text and the last confirmed saved version. Indicate unsaved changes and show whether saving is in progress or failed. If autosave is used, define its timing and ordering so an older response cannot overwrite a newer edit.

Protect the transition to generation

Generate from a known saved script version. Explain when a save is required and preserve the draft after errors. Handle navigation away according to the product’s draft policy. Test rapid edits, delayed responses, and a failed save followed by another edit. Verify that both the editor and downstream job reference the same intended version rather than whichever response arrived last.