When a session goes through the direct archive process but both: (1) fails to archive, and (2) fails to get moved back to the prearchive, it ends up back in the direct archive history in ERROR state. This should be quite rare (I've only seen it once so far), but there isn't any way to acknowledge/dismiss/delete the row. In a production system, you might get a few of these start to build up and annoy users as they choke out real data. Maybe we should have a delete option? Some open questions:
- Should it just be admin-only? This should be a rare occurrence, so limiting it to admins seems quite reasonable.
- Should any session in the direct archive table be deletable? That is, what if it's in RECEIVING/ARCHIVING state? Or should we only have it for ERROR state?