← All traces
Spam blocked at capture
A submission Inkwell scores as spam. The pipeline stops at hop one — by design.
3c5889f91b95991c8fc4844e34ef19286 spans · 96ms total · 0 retriesbridged- mainlineorchestrate
5 hops, bridged
96ms - inkwellcapture
blocked — spam score 0.97 above threshold · HTTP 422
96ms - webhook-relaydeliver
upstream hop did not complete
0ms - switchyardroute
upstream hop did not complete
0ms - distilldedup
upstream hop did not complete
0ms - splitstreamattribute
upstream hop did not complete
0ms
6 hops brokered by Mainline. Inkwell cannot send an Authorization header or emit Webhook Relay’s envelope, and Webhook Relay and Switchyard sign with incompatible schemes — so this console stands in the middle. That is why every hop parents to the root instead of chaining. What changes when they can talk to each other.