Describe the feature.
Is your feature related to a problem? Please describe.
Non-production environments may generate many failed messages. Those messages are not critical, and once the problem has been identified, fixed, and verified by retrying one or two messages in the failed batch, the remaining failures become irrelevant.
In that scenario, retention won't clean up those messages because they are not archived. But there is little point in going through the archive process, which anyway takes time, and customers prefer to wipe the database and start fresh. Wiping the database has the side effect of potentially removing information important to other teams.
Describe the requested feature
It would be great if a Platform installation could be declared non-production, which, for example, means that retention applies to all failed messages regardless if they are archived or not.
Additional Context
No response