Home Search Pricing Get inErrata About

Sign in Sign up

Graph/671a05e9-60b2-40ae-9801-f24f07659e76

Symptomunvalidated

HTTP 504 Gateway Timeout

671a05e9-60b2-40ae-9801-f24f07659e76

HTTP 504 Gateway Timeout

Node Details

Public graph metadata

Updated4/30/2026

PageRank0.0000

Effectiveness0.000

Connections

8 linked nodes

MANIFESTS_ASProblem

i want to replce npm with pnpm with no luck — this dockerfile with some scripts that will install a nextjs app. Outcome: RUN npm install -g npm.

MANIFESTS_ASProblem

We had an error 504, 502 trying to get the dependencies — npx pnpm install. Outcome: Will retry in 10 seconds.

MANIFESTS_ASProblem

when try to post a request to api/webhooks I get 504 error gateway timeout — [POST] [middleware: "middleware"] /api/webhooks status=200 then get [POST] /api/webhooks status=504. Tension: Task timed out after 10.02 seconds. Outcome: After adding access from anywhere in mongoDB cluster this issue was also solved.

MANIFESTS_ASProblem

Sentry is still sending error/crash events from React Native when the app is running in development mode, including native-side crashes. Disabling Sentry via `enabled: !__DEV__` or conditional `Sentry.init` was not sufficient for native errors.

MANIFESTS_ASProblem

errors with 502 and 504 HTTP codes are ignored by Sentry — I'm using Sentry to catch errors in my React app. Tension: some React errors are ignored too. Outcome: I'd like to override this behavior.

MANIFESTS_ASProblem

I would like the ability to see these rules — Sentry has the ability to setup a rule to ignore errors for a certain duration (1 day) or occurrence (< 10 times). Tension: is there a UI or programmatic way to access these? Outcome: Not sure there's a specific API to get this.

MANIFESTS_ASProblem

This particular set of mysterious errors has been asked about on Sentry's GitHub — they reference a WebKit issue. Tension: they are caused by an error coming from a Safari browser extension. Outcome: can safely be ignored, or filtered.

MANIFESTS_ASProblem

the application simply stops responding to webhooks and starts returning a 504 error — running on GCP's Cloud Run. Tension: The only way to "restore" the service is by restarting the Cloud Run container. Outcome: The last message is "Instantiating PubSub client...", then the POD stucks.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata