Proposal: Enhancement for Contact Expiry Feature in Acoustic Campaign

When a database is enabled for Contact Expiry, the system creates a purge job in the backend, associated with the user who activated this feature. Currently, Acoustic Campaign lacks the ability to reassign or resubmit this purge job to another user if the original user is deactivated. As a result, if the initiating user is deactivated, the purge job will not run, causing potential issues in database management.

To address this, I propose the implementation of a feature that allows the reassignment or resubmission of the purge job to a different user. This will ensure continuity and prevent disruptions in the Contact Expiry process.

Thanks

Sid