Looks like you can get a bit of a Node stack trace on mobile
```
Error: Choose failed Missing field "user_id" in context for bucket_val = user_idError: Choose failed Missing field "user_id" in context for bucket_val = user_id
at Decider.choose
(/src/packages/applications/monolith/bin/index.cjs:19115:41)
at isCustomFeedsDisabled
(/src/packages/applications/monolith/bin/index.cjs:266576:32)
at Object.shouldInclude
(/src/packages/applications/monolith/bin/index.cjs:266612:66)
at Resolver.shouldIncludeChild (/src/packages/applications/monolith/bin/index.cjs:175841:26)
at /src/packages/applications/monolith/bin/index.cjs:175901:40
at Array.reduce (<anonymous>)
at Resolver.iterate (/src/packages/applications/monolith/bin/index.cjs:175899:22)
at Resolver.iterate (/src/packages/applications/monolith/bin/index.cjs:175938:55)
at Resolver.iterate (/src/packages/applications/monolith/bin/index.cjs:175938:55)
at Resolver.iterate (/src/packages/applications/monolith/bin/index.cjs:175938:55)
Very few of these public status pages are tied directly to the metrics. They get updated when an internal incident has been created, triaged, and a comms person has put together the status message to communicate.
I mean, think about it, would you want something like this to create a massive "all endpoints down" incident when you have a metrics pipeline issue? For a public company with shareholders?
7 comments
[ 4.0 ms ] story [ 34.2 ms ] thread```
```Now it says "elevated error rate on many frontends." I guess the web/browser is one of many frontends
I mean, think about it, would you want something like this to create a massive "all endpoints down" incident when you have a metrics pipeline issue? For a public company with shareholders?