502 Bad Gateway on Deploy

[daltonch]

We have restructured our API to use microservices and as a response to various threads on the apigee forum we decided to make RPC calls to AWS Lambda using a node proxy and the a127 framework. However we are now unable to deploy our proxy due to an error received when running a127 project deploy,

Deploying project xxx to xxx-dev...
`
Error: Error uploading resource /node_modules/express-session: 502

<title>502 Bad Gateway</title>

502 Bad Gateway

---

nginx ` The node_module it fails on changes but the 502 Bad Gateway error stays the same. This is causing a major issue in our deployment pipeline as we sometimes deploy 5-10 API changes a day and now we are no longer able to do this. What is the expected timeline to fix and what are the possible workarounds?

Thanks,
Chad

[brunodomenici]

Same problem here...