At one of our clients, the persistent state object payload is quite big, that’s why we only save lookup keys in the ps object, and the payload is persisted and retrieved explicitly when needed by sql adapter calls in another dedicated db table.
Upon process completion, the payload is removed again from this dedicated db table (clean-up).
However, when objects are deleted using the delete button in E2E console, the clean-up routine does not take place, and thus the payload oracle table contains orphans.
Any idea how to improve this? Only thing I could think of is a scheduler that checks for orphans regularly…