pfSense

The way AutoConfigBackup queues and batches uploads (once per minute), a sufficiently fast system on a sufficiently fast connection may end up creating multiple backup entries with identical timestamps even though they are tracked to a tenth of a second when assigned by the server. This can lead to some confusion in the ACB GUI if a user attempts to view/delete/etc one of multiple backups with an identical timestamp.

The service returns the last (newest) entry when viewing, which is almost always the one the user intended. When deleting, it deletes all entries with the same timestamp.

It's been this way for years and hasn't had a significant impact that anyone has noticed, but it's worth working around anyhow. Typically the previous entries in these cases are automated intermediate config writes that are not important anyhow.

Simple fix is to introduce a small delay between batched uploads. This not only makes sure the timestamps are unique, but also reduces the load on the server by slowing down batched upload requests.

I have a fix for this pending along with other ACB work.