A realtime publish alone cannot deliver device-status notifications reliably to an offline support dashboard. A support agent opens the live view after a customer calls; the device looks online, but its last status is old. The page fires because the dashboard and the durable record disagree, not because the publish returned an error.
TL;DR: a successful realtime publish is not a delivery receipt. Delivery requires a subscriber; a publish with no subscribers can succeed and deliver nothing. For device status that must survive an offline browser, write a durable inbox record first, publish a low-latency hint second, and read the inbox whenever the client connects. Retrying the publish does not make it durable.
The operating rule is short: Postgres owns recovery; realtime owns speed. Presence helps decide what an operator sees now, but it cannot replace the record of what the operator missed.
Infrai can carry the low-latency hint in this design through one plain REST call, with no Go SDK to install.…