Google Sheets Integration: Create a new row for edited submissions

This is a tricky one!
I have a Jot form to Google Sheets automation set up where when I update an existing Jot form submission, it will update the existing Google Sheets entry. However, that means whenever I edit a current submission, it will erase the previous entry. I want to keep that entry. We need an automation that would create a new row somewhere on a Google Sheet whenever it senses an update. So it keeps the previous entry and creates a new one.

For example a submission comes in, data gets recorded, but going back and making an edit to that submitted data also gets recorded on a new line or shows an edit history etc.

Here is what we tried:
Grabbed an extension called sheet automation and created another sheet called source sheet and set the options to watch for changes and copy the row to another sheet called target.
Now new data comes from jot form from the form submission then into that new source using =IMPORTRANGE> pulls data> extension script watches for changes> target gets copy of new row and target becomes immutable on NEW submissions.

The problem is this method relies on =importrange to read data, but old data changed on this side does not get recorded since it would "overwrite" the target sheet's data. I need a copy to a new row option if that even exists?

To summarize the automation currently just updates the current submission on Google Sheets thus erasing the previous entry. Can't edit the form submissions directly, so using importrange on aznother sheet to run my manual changes, but I also want to make sure the previous entry doesn't disappear.
Is there anyway to make what we want function from the beginning, so we can retain our entry changes while updating them at the same time?

Hi Gibson,

Thanks for reaching out to Jotform Support. Unfortunately, the feature you're looking for isn't available at Jotform right now. We've gone ahead and escalated your request to our developers, but when or if it's developed depends on their workload, how viable it is, and how many other users also request it. If there are any updates, we’ll circle back to this thread and let you know.

Thanks for your patience and understanding, we appreciate it.