“Send test” on a webhook now tells you what actually happened
Test sends are synchronous and report the real status code and response body, instead of a 200 that meant nothing.
Sending a test event to a webhook endpoint used to queue it in the background and immediately report success. That success meant only "we accepted the request" — not that your endpoint had received anything. If your endpoint had been auto-disabled after repeated failures, the test was dropped entirely and we still showed you a green result.
Test sends now happen synchronously and show you what your endpoint really answered: the HTTP status code, the response time, the response body, and the error if there was one.
Two smaller changes that make debugging less painful:
- Test sends work against disabled endpoints, so you can confirm a fix before re-enabling.
- Test sends never count toward auto-disable, so debugging can't push an endpoint over the failure limit.
Building against the API? The response shape of POST /webhooks/{id}/test changed — branch on
delivered, not on the HTTP status of the call itself. Full detail is in the
API changelog.
