Help choose the next Webhook Lab feature: what would save you the most debugging time?

[DimaGutierrez]

If you could add one thing to this workbench, what would it be?

The current version captures events, shows their payloads and sanitized headers, and records manual replays. The next iteration should solve a specific debugging problem.

Here are three candidates from the roadmap:

Option	Proposed improvement	Useful when…
A — Live inbox + search	See new events without refreshing and search beyond the loaded page	You are tracing many incoming events
B — Compare replay attempts	Make differences and failure context easier to inspect	A replay succeeds but you cannot explain why
C — Durable retries	Background delivery with bounded backoff and recoverable jobs	Your local receiver is temporarily unavailable

These are proposals, not existing capabilities or committed release dates. Option C needs more infrastructure and crash-recovery testing than the first two.

Add your vote as a comment—with the reason

My pick: A / B / C / another idea
The task I am trying to finish:
What makes it difficult today:
A concrete example, using fictional data:

What would make you use Webhook Lab twice, rather than try it once? That answer matters more than the letter you choose.

If you want to contribute, mention whether you would prefer to improve Python code, the UI, docs or tests. Start with the contribution guide. A reproducible bug belongs in Issues; feature tradeoffs and questions belong here.

Respuestas en español bienvenidas. Elegí una opción y contame qué problema concreto te resolvería.