no-start-ma on delta import clears delta file

[IAmStevenJohnson]

We often get "no-start-ma" errors on delta imports and when we do, it clears the delta file so a full import must be run to get the recent export changes. Is it intentional, and necessary, that the delta file is cleared on this error? Or would it be possible to change this so when this error occurs, it doesn't clear the delta file so another delta import can be attempted? That's assuming this error is a glitch and retrying might help. I guess if it's definitely not a glitch and this error means a full import is necessary, a change of this nature wouldn't help.

[ryannewington]

@IAmStevenJohnson the delta should only be getting cleared after a full import. What's the cause of the no-start-ma error you are getting?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs.

[IAmStevenJohnson]

I'm sorry for not responding sooner. The original issue is that we often have failures when trying to delete extended schema attributes in Google. They either just don't delete or error. I haven't investigated enough to determine how consistent it is but it's happened for many years. So instead of deleting the various attributes, I was trying to set them to an empty string. That is what causes the delta import to fail. I think it says there should be a value to import but the empty string doesn't provide one and it fails. So I've stopped trying to write an empty string and I think I'm going to just write some real value since deleting them doesn't seem to work reliably.
But I am curious if you, or anyone, else have seen this problem of deleting extended schema attribute values? If happens with both direct (checking the Allow Nulls box) and coded attribute flows.