I run Asermu , a novel-writing app built with Next.js and deployed as a Docker image on Railway. I added Sentry a while ago. The dashboard stayed quiet, and I took that as good news.
It wasn't. Today I found that server-side Sentry had never started in production . Not once.
The clue
I keep a flag-gated test route that reports a test error to Sentry on purpose. On the server runtime it returned:
{ "sent" : true , "runtime" : "nodejs" , "eventId" : "309ea78..." , "flushOk" : false }
Enter fullscreen mode
Exit fullscreen mode
captureException happily handed back an event id. But Sentry.flush() returned false , and nothing arrived in Sentry. The same test on the edge runtime returned flushOk: true , and its event showed up in Sentry.
In 90 days, Sentry had received exactly one event: my own edge test. Zero real server errors is not the same as zero errors.
Ruling out the network
My first guess was Railway's outbound network.β¦