Failed archive copy at filing: retry and alert, or block the filing #57

Closed
opened 2026-11-02 17:07:47 +00:00 by spencerm · 2 comments
Owner

At filing, the sealed data book, the packet's documents and a manifest are copied to the archive folder on the QNAP share (issue 7).

Built as the default: a failed copy never blocks the filing. The worker retries after 5, 15 and 60 minutes, then hourly, and raises an alert to Admin after 3 failed tries or a failed folder check. Admin, Storage, File locations shows the failures and has "Retry now". Turning the archive on later also copies the earlier filings.

To answer: keep, or use the stricter rule: the copy must succeed before the packet counts as filed.


Plan reference: Q53 in docs/PLAN.md (open questions; on main once PR 55 merges). Answer here; the build takes the default until then.

At filing, the sealed data book, the packet's documents and a manifest are copied to the archive folder on the QNAP share (issue 7). **Built as the default:** a failed copy never blocks the filing. The worker retries after 5, 15 and 60 minutes, then hourly, and raises an alert to Admin after 3 failed tries or a failed folder check. Admin, Storage, File locations shows the failures and has "Retry now". Turning the archive on later also copies the earlier filings. **To answer:** keep, or use the stricter rule: the copy must succeed before the packet counts as filed. -------- Plan reference: Q53 in [docs/PLAN.md](https://gt.pescoinc.biz/spencerm/PacketStation/src/branch/main/docs/PLAN.md) (open questions; on main once PR 55 merges). Answer here; the build takes the default until then.
spencerm added the phase 10decision: Seth labels 2026-11-02 17:07:47 +00:00
Author
Owner

The copy must succeed before the packet counts as filed. If a copy fails, then the admin must be notified with details, and the packet kept in the previous stage so that it the filing flow can be attempted again.

The copy must succeed before the packet counts as filed. If a copy fails, then the admin must be notified with details, and the packet kept in the previous stage so that it the filing flow can be attempted again.
Author
Owner

Recorded as open question 53 in docs/PLAN.md and built in PR 59: FILE copies inside the filing transaction; a failed check or copy rolls the filing back (packet stays in its previous stage), the person filing sees why, and Admin gets the critical archive_failed alert for that packet with who tried, the folder and the error. Filing it again once the archive works files it and clears the alert.

Recorded as open question 53 in docs/PLAN.md and built in PR 59: FILE copies inside the filing transaction; a failed check or copy rolls the filing back (packet stays in its previous stage), the person filing sees why, and Admin gets the critical archive_failed alert for that packet with who tried, the folder and the error. Filing it again once the archive works files it and clears the alert.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spencerm/PacketStation#57