Too bad you don't explain why this "element" would transition from the first state to the second state – that information might help. Since that isn't specified, however, I'm going to make an assumption: that the "element" goes into this middle state after some period of inactivity.
If that were the case, you could use:
If instead the element goes into this state when, say, a balance goes to zero, you could use:
I think part of your problem stems from your choice of words for the first state: Normal. The opposite of normal is abnormal – but that's not a very good name for this state. (I suggest trying to find a more descriptive name for the first state, and seeing if that leads to a better name for the second state.)
As a footnote, if you don't mind using a little irreverent humor, you could try:
Collins defines that word as:
purgatorial (adj.) a place or condition of suffering or torment, esp one that is temporary
I'm assuming this middle state is temporary; that the element's state will revert back to normal or to deleted within a relatively short time.
Wiktionary defines purgatorial as “Of, pertaining to, or resembling purgatory”, and purgatory is defined in one dictionary as:
purgatorial (n.) Any place or state of temporary suffering or oblivion.
By the way, this suggestion probably wouldn't be appropriate if the user would ever see the name of the state in a notification. However, if it was only used as a state name inside the software, it might work. (Presumably, the user would see Pending Deletion, or something like that.)
It's not an ideal candidate by any means, but you've given us a very tall order with: One-word synonym for “this is going to be deleted”. In the absence of such a word, please don't be offended by a stretch. Though "temporary oblivion" might never make it into your code, I still thought it was an interesting concept to explore.