Logging user actions

When something goes wrong with a publication, the user's first question is "what actually happened?" Being able to answer that question is not just convenience — it builds trust in the product.

We implemented an activity log that records key events: when a post was created, queued, sent for publication, and what the platform returned.

This isn't a technical log for developers — it's an understandable history for the user. The difference is in what gets recorded and how.

The value showed up surprisingly quickly: on the very first incident we had all the information we needed.