manut reported an issue where visiting the /logs page in a fresh dev container triggered a flood of ActionController::RoutingError (No route matches [POST] "/srv/se") errors. The user traced the problem to the human-activity-tracker.js service. NateDhaliwal confirmed seeing similar errors randomly in the browser console on their non-ESR dev instance, while nat acknowledged the report and informed the team.
tgxworld announced that the issue was fixed by kris.kotlarek and backported to version 2026.7. Regarding NateDhaliwal’s experience, tgxworld clarified that such requests should not occur by default in development environments unless specific ENV variables are set. NateDhaliwal later noted the errors had stopped appearing, possibly due to already having the fix or previous transient states, though they observed a separate Content-Length-Mismatch error unrelated to this thread. manut thanked the team for the quick fix and confirmed they would verify the resolution in the next 2026.7.x release.
On a fresh dev container:
ActionController::RoutingError (No route matches [POST] "/srv/se")I tracked down the issue to /frontend/discourse/app/services/human-activity-tracker.js.
I’m getting this fairly frequently on my dev instance too (not on ESR). It just logs in the browser console randomly. Weird.
Thanks for letting us know.
I’ve informed the relevant team about this, though it might take a bit of time for a response here.
Thank you for the report!
@kris.kotlarek Fixed this in PERF: Reduce session engagement beacon traffic - Pull Request #42712 - discourse/discourse - GitHub and I’ve just backported the fix to 2026.7
By dev instance, do you mean your development environment? The /srv/se requests should not be happening in the development environment by default unless a particular ENV has been configured.
Hmm… it’s not there now, but I was sure I’d seen it previously.
OP also used:
soo…
You might have seen it before PERF: Reduce session engagement beacon traffic - Pull Request #42712 - discourse/discourse - GitHub was shipped. If you see it again while running the latest version. Let me know 
Perhaps it was that. I also see Frequent ERR_CONTENT_LENGTH_MISMATCH errors in browser console in dev environment but that doesn’t look like it’s been remedied by any of this.
Thanks for the fix, that was quick!
I’ll let you know if it fixed the issue on the next 2026.7.x