Staging environment returning 504 errors.

hello! we are using our staging environment as a host and i can load plasmic pages locally and in production using it. however, we’re getting 504 errors when we try to access some pages with the staging environment url. this happened sometime last week and seemed to resolve itself, but it’s happening again today, and i’m not sure why.

hi! what’s your project id?

this is one of them! <removed>

hmm I’m not seeing issues for that project… can you paste any stack traces that you see?

i wasn’t able to see anything for that error, but another page is giving back a 500 and this is what we have for it (with the project ids removed):

FetchError: request to <> failed, reason: socket hang up
    at NodeClientRequest.<anonymous> (/app/node_modules/next/dist/compiled/node-fetch/index.js:1:65756)
    at NodeClientRequest.emit (node:events:525:35)
    at NodeClientRequest.emit (/app/node_modules/@mswjs/interceptors/lib/interceptors/ClientRequest/NodeClientRequest.js:327:38)
    at TLSSocket.socketOnEnd (node:_http_client:518:9)
    at TLSSocket.emit (node:events:525:35)
    at TLSSocket.emit (/app/node_modules/dd-trace/packages/datadog-instrumentations/src/net.js:61:25)
    at endReadableNT (node:internal/streams/readable:1358:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

what’s the project id? :sweat_smile:

ohh sorry! i’ll dm them!