It would have to halt on the error, sure. There could be many edits *after* the error which are dependent on the edit which caused the error, so all of those could not be processed either. Determining which edits are dependent on the error is a processing overhead. It may not be much, but it would slow down saving. Even slower when trying to determine which edits are not dependent on the error and can still be processed.

bart99gt wrote:What needs to be changed more than anything is that WME needs to stop halting on a save error.

To explain, WME needs to process all valid edits up to the error, note the error, then process all valid edits AFTER the error. The only thing that shouldn't be saved is the error itself, and honestly, a simple dialog saying "this edit was not saved due to a saving error" and HIGHLIGHTING the error with some consistency (something that has been lacking in WME for at least a year) would suffice.

This sounds like it may cause the servers to have to do extra work which may slow it down. The possibility of losing tons of work due to an error should teach an editor a valuable lesson early on: save your work often. Besides, upon coming upon a save error, rather than just reload the page, one could simply press the "undo" button until they were able to save their work, at which point they'll also learn what was the edit they attempted that was not allowed, since the edits are undone one at a time.

Sent from my SM-N920P using Tapatalk

I thought throttling was based on quantity. Does it matter how often you save? If the limit is 100 edits in an hour, does it matter if you save 100 edits at once, 25 four times or 10 ten times?

Sent from my SM-N920P using Tapatalk

What needs to be changed more than anything is that WME needs to stop halting on a save error.

To explain, WME needs to process all valid edits up to the error, note the error, then process all valid edits AFTER the error. The only thing that shouldn't be saved is the error itself, and honestly, a simple dialog saying "this edit was not saved due to a saving error" and HIGHLIGHTING the error with some consistency (something that has been lacking in WME for at least a year) would suffice.

APettyJdabrowntrucka wrote: The possibility of losing tons of work due to an error should teach an editor a valuable lesson early on: save your work often.

Which is a great idea until you realise that saving too often will trigger throttling.

I don't know any more than what I have read in some of the forum topics that suggested that it can be triggered by times as short as one minute.

bart99gt wrote:What needs to be changed more than anything is that WME needs to stop halting on a save error.

This. 110%.

My interpretation of the halt referenced here is when the entire screen went dark, unselectable, and no feedback from WME of the problem. You then had to completely refresh the browser to get response back. That should not ever happen, even in an error condition.

WME should produce the error message and allow correction of the error. Sometimes, correction of that error will require undoing the steps done after that error, but at least it's allowing you to make the correction. At that time it was not, but for what it's worth, I haven't noticed any problems with this since the latest update to WME.

The thing I have found that causes the most errors is cutting segments.
Cutting a new segment IS NOT POSSIBLE.
Cutting a segment more than once between saves IS NOT POSSIBLE.
Avoid cutting the same segment (even its children) more than once per save. You'll notice your save errors will reduce to almost none...

Cant help you with places.. they keep adding data validation to them thinking that is helping.. it only annoys us in the editor because you can obviously add this junk from the app with 0 data validation.