I don’t know how to delete this, but if you have a similar problem the issue was the upstream service. Though I cannot say exactly why this was happening.
The service now only runs an EQS query and if it returns anything it sets the return to the key, or clears if it fails.
Previously, the service was much longer. It checked for similar actors (an older version that used a different class, and was no longer present at all) with a specific tag after the EQS query succeeded but also if it failed. I’m thinking the strange behavior has something to do with a redundant check after an Is Not Valid which would check for the class that was no longer present, and this was somehow setting the key to None-ish? (but not really None). Otherwise I can’t explain this at all.