Hey all! I’m Zack, a product designer on Workbench and Event Destinations.
Some feedback we’ve heard consistently about webhooks and event destinations is that we could do a better job displaying information in the event deliveries list when viewing an event destination. More specifically, developers wanted more details about delivery attempts, including which attempts were failing, but were eventually successful.
To hopefully address some of that feedback, I’ve been exploring some updates to the delivery attempt status badges and would love your feedback!
Delivered
When an event is delivered successfully, the delivery attempt receives a status of Delivered
.
The delivery attempt was successful
Failed
When an event is delivered unsuccessfully, the delivery attempt receives a status of Failed
.
The delivery attempt has failed and there are no more automatic retries.
Pending retry
When a delivery attempt has failed, but will be retried automatically, the badge color and icon are updated while the label remains Failed
.
Several delivery attempts have failed, but are scheduled to be retried automatically.
Recovered
When a series of delivery attempts for the same event fail, but eventually succeed, the badge color and icon are updated while the label remains reflective of the original attempt status, either Failed
or Delivered
.
The successful attempt in a series of failing attempts.
A failed attempt in a series of failing attempts that have recovered.
Any and all feedback is welcome, but I’m most interested in learning:
- Do the icons effectively communicate the status of the delivery?
- Does the introduction of new colors for both pending retries and recovered deliveries help or does it add confusion?
- What other information about the delivery attempt would be helpful to see at-a-glance in the list view?
Thanks y’all and looking forward to hearing from you!
-Zack
3 Likes
The green, red and orange labels all seem very clear to me, especially due to the matching icons.
The blue labels were a bit confusing for me at first glance though. Only after reading the context did it become clear that they were all part of the same event. To be honest I didn’t really notice the icon for these ones. Maybe a different text for the labels could be helpful here. Something like ‘Initially failed’ comes to mind but I’m not sure that would fit
.
I think it would also be helpful to make it somewhat easier to distinguish the failed events from the final one that succeeded. Ultimately I don’t really care as much about a failed event if it got delivered in the end anyway. Maybe it would even be fine to make those attempts greyed out of sorts.
1 Like
Thanks for the feedback @jespertheend and I totally get what you’re saying!
I had originally introduced the term ‘Recovered’ and used to that to replace the Failed/Delivered label once a delivery was successful, but it felt like it was hiding the original status a bit too much and almost rewriting history to some degree.
Here’s another option I was exploring that pulls the icons out of the badge and into their own column. This option keeps the badges consistent, while also highlighting any recovered deliveries
1 Like
Ooh I think I like this a lot better! I think blue color was mostly what made it unclear to me. Whereas with green and red it seems much more representative of what actually happened.
As a side note, it would be nice be able to see at a glance which delivery attempts belong to the same event. My first thought was to draw some kind of line or connection in order to group them together. But I suppose that won’t really work once attempts from other events start getting sandwiched in between.
So maybe another option is to highlight attempts when you hover over them. Chrome DevTools does something similar with network requests. If you hold shift while hovering over requests, it highlights the initiator and dependencies.
1 Like
@jespertheend Yes!! I actually had explored some options related to grouping related deliveries together. You could essentially toggle this view or a flat list view (like it is today), or some other options I had would highlight the related attempts once you selected one in the chain.
It’s a little out of date, but here’s the toggle view option I had explored:
Oh wow that actually looks really nice haha. I think this one is the most clear so far. Any reasons why you ended up abandoning this?
Ah thanks! Yeah we had some pretty good excitement about this kind of view originally, but I don’t quite remember why it didn’t get implemented 
Based on our convo here, I brought it up with our team this morning and we’re all sounding pretty excited about it again, so hopefully we can push on this a bit more!
1 Like