Split status "delivered" into "pushed" and "received"

[bablokb]

Currently, the history shows dashboards pushed to the client as "delivered", even if the client is offline and did not fetch the dashboard yet.

Certainly not a high priority idea.

[dmellok]

Fair terminology point. Splitting "pushed" (retained slot written server-side) from "received" (client actually fetched) is doable. For REST clients we already log every /frame GET, so cross-referencing a push event's digest against the next fetch from the target device would flip the status retroactively when the fetch lands. MQTT is murkier without broker-side delivery acks, but the client's next heartbeat carrying the current digest could serve the same signal.

One question: if a client stays offline for a while, should "pushed" stay sticky forever (accurate but reads like it never got there), or expire after some window? Superseded is arguably its own case too, a newer push overwrites the retained slot, so the old one will never be fetched.

[bablokb]

I would keep it simple and don't expire. The pushed is the last state and the admin can delete the push using the delete button (which would do a bit more than only deleting the entry from the history in this case). A new push should delete any pending old pushes.