Right now, when users delete drafts, they are soft deleted. After a grace period, which by default is 1 hour
, they are hard deleted, meaning the draft and its PID are fully deleted from the database and OS with no way of getting them back besides a full DB backup recovery.
We should consider/discuss whether to increase this to something substantially higher, e.g. 24-48 hours, in order to allow recovering accidentally deleted drafts when users ask for it.
The deletion task runs every 60 minutes, which is fine. The 60 minutes here is not relevant, only the grace period itself.
Also, maybe we should prevent deleting drafts that were in a request. E.g. if a draft is submitted and then the request is declined, the user should not be able to delete the draft.
Right now, when users delete drafts, they are soft deleted. After a grace period, which by default is 1 hour
, they are hard deleted, meaning the draft and its PID are fully deleted from the database and OS with no way of getting them back besides a full DB backup recovery.
We should consider/discuss whether to increase this to something substantially higher, e.g. 24-48 hours, in order to allow recovering accidentally deleted drafts when users ask for it.
The deletion task runs every 60 minutes, which is fine. The 60 minutes here is not relevant, only the grace period itself.
Also, maybe we should prevent deleting drafts that were in a request. E.g. if a draft is submitted and then the request is declined, the user should not be able to delete the draft.